Frontend: Rename pipeline type labels for `merge train` and `detached`
Related to #217718.
There are two main problems with how we identify and differentiate between the merge request, merge result and the merge train pipelines in GitLab.
The "detached" label for the merge request pipelines is confusing. This label is not understood by many users, and it's been surfaced in UX research. See this comment for the UX research insights.
Addressing the bug alone won't solve the problem of confusion caused by the "detached" label. We need to introduce human-readable labels for the different pipeline types and provide additional information about each type so users can learn about them from the UI.
We will introduce new labels for the pipeline types and rename the
Each label will show a tooltip on hover with the appropriate description.
Note: Some of these may need backend work.
detachedlabel -> Change to
This pipeline ran on the contents of this merge request's branch, not the target branch.
- Unlabeled merge train pipelines -> Add
This pipeline ran on the contents of this merge request combined with the contents of all other merge requests queued for merging into the target branch.
This is linked to Backend: Make it easier to understand and diffe... (#217718) Please check there as the main source of truth and related backend work. This is just an implementation issue for the frontend. There's additional work to be carried out in Frontend: Introduce new pipeline label for Unla... (#353090) but this is blocked by backend data.
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.