Merge train visualization: Improve the warning for merge request removal to communicate impact
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
Once we have the ability to make approximate prediction for time to merge using a merge train - #454181 - We should also make changes to the current warning displayed when users remove an item from an active train. The warning should inform users of the impact the removal can have on the other items queued before and after it so they can make an educated decision.
Warning displayed today:
Intended users
User experience goal
The warning should inform users of the impact the removal can have on the other items queued before and after it so they can make an educated decision.
Proposal
TBD
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.