### Problem to solve We are introducing a first class Releases concept, which is great. We should extend this to also stats on how many errors were reported as new in this release, as well as how many were resolved. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [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) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details This work supports the [Error Tracking Vision](https://about.gitlab.com/direction/monitor/debugging_and_health/error_tracking/). ### Proposal On this page we can show simply the summary number, and clicking on that number will take you back to the issue list filtered by that release. https://gitlab.com/gitlab-org/gitlab-ce/issues/56045 ### Permissions and Security ### Documentation Documentation Required, most likely [here](https://docs.gitlab.com/ee/user/project/operations/error_tracking.html) ### Testing ### What does success look like, and how can we measure that? ### What is the type of buyer? ### Links / references <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->