Repository analytics project page is inconsistent and not easy to read

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

The Repository analytics page for a project has an inconsistent layout compared to our other analytics pages and is not easy to read. We will improve the layout and overall UX for this page.

Problem to solve

The Repository analytics page for a project has an inconsistent layout compared to our other analytics pages and is not easy to read.

• The branch/tag filter applies to both code coverage and commit statistics even though that's not clear by the placement.
• When you do use the filter ^ it refreshes the whole page and you lose context of where you were.
• A text link shows up near the filter ^ that brings you to a full list of commit for the branch, but does not indicate what it is for.
• Charts shows up near the text link ^ and leads to a 404.
• Code coverage and commit statistics have titles that change depending on the filter that is applied, and also include the date range in their title, even though it is represented on the graph.
• All charts are stacked vertically for commit statistics which makes it very difficult to read and parse.

Here's an example: https://gitlab.com/gitlab-org/gitlab/-/graphs/master%2Fcharts/charts

Intended users

• Delaney (Development Team Lead)
• Presley (Product Designer)
• Sasha (Software Developer)
• Sasha (Software Developer)

Metrics

User experience goal

Improve the UX by unboxing, improving layout, fixing bugs/inconsistencies and increasing readability.

Proposal

Explore design concepts to improve the page readability and layout. Some possible proposals below.

• Move each page to it's own tab.
• Relocate filters so they are clearly applying to the whole page.
• Emphasize actions (if there are any) and increase clarity of what they do.
• Update the components to match Pajamas.
• Unbox the UI

🎨Designs in design management

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

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

What is the type of buyer?

Is this a cross-stage 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.