DORA

Use this page to open each individual DORA metric report.

DORA Overview

The DORA Overview report measures system performance using the four DORA metrics: Lead Time for Changes, Deployment Frequency, Change Failure Rate, and Mean Time to Restore. It is accessible under Delivery in the left sidebar.

The overview displays all four metrics as individual charts, each showing the current period trend compared to the previous period. Each chart displays the median value, the previous period value, and the change between the two.

• Lead Time for Changes - The total time it takes for a code change to go from the first commit to being successfully deployed to production.
• Deployment Frequency - How often code is successfully deployed to production.
• Change Failure Rate - The percentage of deployments that result in a failure requiring remediation.
• Mean Time to Restore - The time it takes to recover from a failure in production.

Each chart can be toggled between Line and Bar views. Individual DORA metric reports can be accessed directly from the overview by clicking View report on each chart, or from the left sidebar under DORA.

Filters available at the top of the report include date range, Repos, Attributes, Teams, Groups, and Settings.

DORA Entities table

Below the DORA widgets, this table exposes the raw records behind the scores. The widgets tell you what your Lead Time, Deployment Frequency, Change Failure Rate, and Time to Restore are; the table tells you which pull requests, releases, and incidents produced them. All three tabs follow the page's active filters — period, repositories, services, and team — and support search, sorting, and pagination, with rows opening the underlying record.

• View Pull Requests — the pull requests behind Lead Time for Changes, showing title, repository, author, lead time, status, creation date, and whether the PR is ignored in metric calculations.

• View Releases — the deployments counted by Deployment Frequency for the selected team, showing the release message, success or failure, author, and deployment time, so release cadence can be read alongside release reliability.
• View Incidents — the incidents behind Change Failure Rate and Mean Time to Restore, showing type, status, time to recovery, source, and when each incident occurred and was fixed — making the outliers that inflate the averages visible individually.