Expand pipeline dashboard to contain stages
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
With https://gitlab.com/gitlab-org/gitlab-ee/issues/7861 we introduced the cross-project pipeline dashboard as part of the Operations Dashboard. The design for this was mostly focused on collections of microservices that have up-and-downstream dependencies.
As such, if you have such dependencies, the space where the pipeline is displayed is well utilized:
However, if a user does not utilize the feature of triggering and connecting pipelines in such a way, the space is under-utilized:
Intended users
Further details
Expanding the stages within a pipeline, similar to how we show them on the pipeline view (https://gitlab.com/gitlab-org/gitlab-ee/pipelines) will allow users to see more about where the pipeline is at a glance if the space allows.
In fact, the space available to the Operations Dashboard widget is larger than the space allotted to the Stages column on the pipelines page given the same screen resolution
| Operations Dashboard | Pipelines Page |
|---|---|
![]() |
![]() |
dashboard-card-footer is 330px wide on a 1200px wide screen |
table-section-15 is 160px wide on a 1200px wide screen |
Proposal
Expand the widget smartly to utilize the entire space - so that if there is only one pipeline (this project has no upstream or downstream dependencies) then you will see the mini-graph of the stages that you can click on to see jobs just as you do in the /pipelines page.
Permissions and Security
This has no impact on the permissions or security model for this feature.
Documentation
We should update screenshots to match
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
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.



