### Release notes Enhancing visibility for Software delivery performance with a new trend chart for DORA Time to restore service metric. With the addition of the four DORA metrics tiles to the VSA overview dashboard, we are now adding overtime visualization to the "Time to restore service" metric. With this new chart, users will have a better understanding of software stability and reliability trends over time. The new Time to restore service chart shows information about how long it takes an organization to recover from a failure in production. GitLab measures this as the median time required to close the incidents in the given time period. It is the third DORA chart that is available out of the box in GitLab. We plan to keep improving the visibility into DORA metrics and to add charts for the fourth metric - Change failure rate. <!-- 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). " --> ### Problem to solve <!-- What is the user problem you are trying to solve with this issue? --> When viewing the [mean time to restore service](https://gitlab.com/gitlab-org/gitlab/-/issues/299096) metric in VSA, I want to drill in and see more detailed information about my deployments so that I can identify trends and understand deployment behaviors of my teams & projects. Once we implement https://gitlab.com/gitlab-org/gitlab/-/issues/355304 the user will need an overtime visualization for **Time to restore service** Metric. ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> 1. Add a new chart under **CI/CD Analytics** page. 3. Order of the charts tabs (left to right): `Release statistics` - `Deployment frequency` - `Lead time` - `Time to restore service` - `Change Failure Rate` - `Shared Runners Usage` 3. Chart type: same as https://docs.gitlab.com/ee/user/analytics/ci_cd_analytics.html#view-lead-time-for-changes-chart. 3. Tile for "Time to restore service" should also be included in the chart. 3. Chart and tile should be filtered based on Date pickers with 3 options: `Last week`, `Last month`, `Last 90 days`. 4. Trendline with `median time` is needed. 4. Consider performance vs data to ensure smooth page usability. 4. ~"GitLab Premium" will see project level. 5. ~"GitLab Ultimate" will see also see group level.  ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager) * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [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) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor) --> ### Feature Usage Metrics <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> <!-- 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 -->