**Release Notes** With Merge train visualization users can closely track merge train activities and take actions with a better understanding of the impact on other MRs in the queue leading to improved transparency in the merge train. <table> <tr> <th> ### Problem to solve Today, users have no visibility into how many cars are in a train and are in a train. ### Proposal 1. Expose count of cars by branch by project and merge train in Merge Train API 2. Add a page to track progress on merge trains </th> </tr> </table> ## :map:️ Plan (listed by priority and confidence) <table> <tr> <th>Step</th> <th>Purpose</th> <th>BE issue required?</th> <th align="right">Design ready?</th> <th>Milestone</th> </tr> <tr> <td> [Design discussion only - merge train visualization](https://gitlab.com/gitlab-org/gitlab/-/issues/277391 "Design discussions only - Merge Train Visualization") </td> <td>Explore design proposals. Have extensive discussions and feedback sessions to arrive at a feasible proposal. Discuss iterations and create new issues with decided scopes.</td> <td>No.</td> <td align="right"> :white_check_mark: </td> <td>No implementation required. We can close this out.</td> </tr> <tr> <td> [Merge train visualization MVC](https://gitlab.com/gitlab-org/gitlab/-/issues/454179 "Frontend: Merge train visualization - MVC") </td> <td> Deliver the first iteration to users with: 1. List view of all queued MRs 2. List of already merged MRs 3. Ability to remove an item from list view 4. Filter by deployment branch 5. Entry points: Pipeline widget, notification, pipeline detail page </td> <td> [Backend: Merge train visualization MVC](https://gitlab.com/gitlab-org/gitlab/-/issues/454180 "Backend: Merge trains visualization MVC") </td> <td align="right"> :white_check_mark: </td> <td> FE: BE: </td> </tr> <tr> <td> [Merge train visualization: Add estimated time to merge](https://gitlab.com/gitlab-org/gitlab/-/issues/454181 "Merge train visualization: Add estimated time to merge") </td> <td>Add the column in the list view to surface estimated time to merge</td> <td> [BE: Show estimated time to merge for merge trains](https://gitlab.com/gitlab-org/gitlab/-/issues/454355 "Backend: Show estimated time to merge for merge trains") </td> <td align="right"> :white_check_mark: </td> <td> FE: BE: </td> </tr> <tr> <td> [Merge train visualization: Show removed MRs in the list](https://gitlab.com/gitlab-org/gitlab/-/issues/454356 "Merge train visualization: Show removed MRs from the queue") </td> <td>Add a tab for removed MRs</td> <td>Not sure.</td> <td align="right"> :white_check_mark: </td> <td> FE: BE: </td> </tr> <tr> <td> [Merge train visualization: Add an empty state](https://gitlab.com/gitlab-org/gitlab/-/issues/454392 "Add an empty state for merge trains page") </td> <td>A blank state when merge trains are enabled but no active train running for a branch.</td> <td> No. We do need [a foundation issue for illustration](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1805 "Add a new illustration for Merge train page empty state"). </td> <td>In progress</td> <td> </td> </tr> <tr> <td> [Merge train visualization: Add estimated impact in removal confirmation modal](https://gitlab.com/gitlab-org/gitlab/-/issues/454394 "Merge train visualization: Improve the warning for merge request removal to communicate impact") </td> <td>Once we have the ability to predict the estimated time to merge, we should improve the confirmation modal that appears to present the impact of the</td> <td>No</td> <td>TBD</td> <td> </td> </tr> <tr> <td> [Git resembling visualization for merge trains](https://gitlab.com/gitlab-org/gitlab/-/issues/453959 "Git resembling visualization for merge trains") </td> <td>To make the visualization more user-friendly, explore a git like branch representation for the trains running for a target.</td> <td>Not sure.</td> <td>TBD</td> <td> </td> </tr> </table>