Skip to content

Project Quality Summary Page without data

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.

Release notes

Problem to solve

As an app dev team lead, I want to see how quality is trending in my projects, so I can prevent escaped defects and spend time shipping features not bug fixes.

Additional information / use cases

Hypothesis: If we provide high level data from more features to team leads, they will get their team to use the features driving usage.

Experiment: Add data views for data we have about test execution and code coverage, add teaser links that can be tracked for other categories to inform what to develop next.

User experience goal of this iteration

The user should be able to navigate to the page that will hold data implemented as part of &5430

Proposal

  1. Create a tab on the existing Analytics -> CI/CD page for a Quality Summary page
  2. Create the empty page
  3. Add documentation for the new page (place holder)
  4. Wrap it all in a feature flag?

Technical proposal

  • Create a new blank vue component that we'll build the project summary in, something like ee/app/assets/javascripts/project_quality_summary/components/app.vue
  • Put the new component inside of a new <gl-tab> with the title Project Quality in ~/projects/pipelines/charts/components/app.vue
  • Add a new feature flag called :project_quality_summary, push it to the frontend, only display the tab/contents if it's enabled

Documentation

Create some place holder documentation for the new page about what will be on it, this can be iterated on in later issues in the epic.

What does success look like, and how can we measure that?

Acceptance Criteria

  • The page is created
  • The page/tab is available when feature flag is set to display it
  • The page/tab is NOT available when the feature flag is set to not display it
  • UX review done cc @gdoyle
  • Page has a breadcrumb to navigate back to other parts of the site

Available Tier

GitLab Ultimate

Links / references

Edited by Miranda Fluharty