Improve Project CI/CD Analytics page
Release notes
Problem to solve
The Project CI/CD analytics page contains a lot of data that is confusing for the user to understand and identify next steps with when evaluating the health of their pipeline. See more issues that were identified in gitlab-design#2439 (closed). Based on problem validation, we need to refactor the page to allow the user to ingest the data meaningfully and give them an easy way to identify pipeline health.
JTBD we are solving for: When I am managing continuous integration of code at scale, I want to understand the pipeline health, so I can successfully resolve and prevent issues from occurring.
Intended users
- Software developers
- Platform engineers
- DevOps engineers
User experience goal
The user should be able to quickly understand how healthy their pipeline is, specifically focusing on status and duration.
Proposal
Acceptance criteria
Criteria | Current UI | With this proposal | Component needed |
---|---|---|---|
Update single stats on the page | Single stat | ||
Move individual filters on graphs to be universal filters on the page. Add a new filter for pipeline type. Add a new filter for branch. | Combobox | ||
Update page title. | CI/CD analytics |
Pipelines |
N/A just text. |
Update duration chart to be a line graph and to show p50 and p95. Use the color system for categorical data for colors on the graph. | Line chart with legend interaction | ||
Update status graph to include failures, successes, and other (cancelled + skipped) runs. Use custom colors for the graph, successful=dv-green-500 , failed=dv-magenta-600 , other=dv-blue-500 . |
Stacked column chart with legend interaction |
Resources
- Designs in design assets
- Figma file: https://www.figma.com/file/ZjFKeXSfmG2KrWPeb47Slt/Runner-Fleet-Metrics?type=design&node-id=1084%3A2221&mode=design&t=Rfi3JJaT86rlgbvI-1
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
Measuring adoption:
- we track visits to the page today, so we'd want to see an increase.
Measuring if the changes build a better experience:
- Through a feedback banner (tracked in a separate issue). This could also help us figure out which metrics are most important to add next.
What is the type of buyer?
Is this a cross-stage feature?
Yes. grouppipeline execution , grouprunner , groupoptimize
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.
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.
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.
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.