Improve Merge Trains Error Messaging
Release notes
When the merge train fails because of a merge conflict, the messaging doesn't give the user a clear explanation of what happened or how to resolve the issue. This could be improved by improving the messaging, or linking to the docs.
Example:
Intended users
User experience goal
Users should be provided enough information to be able to troubleshoot by themselves.
Proposal
When presenting a system message about an MR being dropped from a train due to conflict, present a link through Learn more and link it to https://docs.gitlab.com/ee/ci/pipelines/merge_trains.html#merge-request-dropped-from-the-merge-train.
More improvements suggested in #368800
Tech proposal
Update the message with a link in ee/app/services/system_notes/merge_train_service.rb
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
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.