Backend: Make it easier to understand and differentiate merge request pipelines
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.
User experience goal
I want to easily differentiate between different pipeline types.
Introduce new labels instead of "detached"
We should introduce new labels for the pipeline types. Each label will show a tooltip on hover with the appropriate description.
- Unlabeled merged request pipelines -> Add
This pipeline ran on the contents of this merge request's branch, not the target branch.
- Unlabeled merged results pipelines -> Add
This pipeline ran on the contents of this merge request combined with the contents of 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.
The FE can change
merge train without any BE changes. For
merged results the FE will need a new flag in place.
The flag should be
merged_results_pipeline letting the FE know when to display the label.
Current flags we have
- #217718 (comment 353987250)
Permissions and Security
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.