Frontend: Introduce new pipeline label for Unlabeled merged results
Related to #217718 (closed).
Problem
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.
Proposal
Introduce new label
- Unlabeled merged results pipelines -> Add
merged results
label-
merged result
:This pipeline ran on the contents of this merge request combined with the contents of the target branch.
-
Further details
This is linked to Backend: Make it easier to understand and diffe... (#217718 - closed) Please check there as the main source of truth and related backend work. This is just an implementation issue for the frontend. Part of the frontend work is in Frontend: Rename pipeline type labels for `merg... (#352939 - closed)
Available Tier
- Free
- Premium/Silver
- Ultimate/Gold
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.