Make pipeline mini-graph representation more useable
Release notes
🧩 Problem
The mini graph displays all the stages and that doesn't scale well in pipelines with many stages. This graph takes up a lot of space on pages like the pipeline list (that's already highly populated) and also the pipeline widget on the MR page.
- There is no mechanism in place to meaningfully collapse the graph into sections in case of many stages
- The trigger jobs are used to trigger another pipeline and do not link to a logs page. This difference is not visually communicated.
- The downstream and upstream pipelines representation end up bloating the visualization
Our understanding from speaking with users so far is, mini pipeline-graphs are helpful in:
- providing a quick overall status of each stage hinting at which ones need attention
- taking users directly to the logs of failed jobs with fewer clicks
Keeping the mentioned insights in consideration, the mini-graph experience requires to be re-evaluated to be more useable for users, leading them to the intended results faster and with lesser number of clicks.Intended users
User experience goal
- Experience provided through mini-graph should be at part with the larger pipeline graph
- Semantic relationships between objects in the product should be rightly represented.
🎨 Proposal(tentative)
- Make mini-graph more concise: Instead of the following, we couldn't just show a summarized version that communicated: X passed, X failed, X running, X paused, X skipped, etc.(By @pedroms)
- Remove links from trigger/bridge jobs that kick-off downstream/upstream pipelines and visually represent the relationship with the triggered pipeline
Or, alternatively, we could “join” stages that have the same status. So two passing stages in a row would be displayed together. Maybe not the best idea, but I hope you get my point.
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.
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.