<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently piloting, details can be found in this issue: https://gitlab.com/gitlab-com/Product/-/issues/1392 and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> The CI pipelines minutes usage as reported on the [Usage Quotas](https://gitlab.com/profile/usage_quotas#pipelines-quota-tab) page only shows the current month usage which is reset every month and there is no way to view activity in past months for analyzing historical usage by monthly and by the project. **Now there are two charts that enable users to view their historical usage of CI pipeline minutes for shared runners to make informed decisions.** ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> The CI minutes usage as reported on the [Usage Quotas](https://gitlab.com/profile/usage_quotas#pipelines-quota-tab) page only shows current month usage which is reset every month and there is no way to view activity in past months for analyzing historical usage by monthly and by project. *As a user whose project consumes CI minutes, I want to see historical usage data so that I can anticipate usage in the current month based past months' activity.* ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> Namespace admin or Group admin should be able to see historical CI minutes usage by month and by project for each month. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> On the `CI/CD Analytics` page (left menu navigation: Analytics > CI/CD) add CI minutes usage data by month and by project in a given month.