DevOps Metrics for JiraJira Cloud · Built on Forge

The four DORA™ metrics on your Jira dashboard

Deployment frequency, lead time for changes, change failure rate and time to restore, calculated from the releases, status changes and incidents already in Jira. No CI/CD setup.

Free for Jira sites with up to 10 users. Larger sites start with a free trial.

Sample data in your browser. Nothing is saved and nothing is sent anywhere. Dashed frames mark the parts that come from the app. Pro features are on, as in the free trial. Real screenshots below ↓
In your Jira

What you get

Screenshots from a real Jira site with sample data.

DevOps Metrics — Overview gadget for the last 6 months: deployment frequency 1.7 per week, lead time 3 days, change failure rate 13% and time to restore 10.5 hours, each with band and arrow; next to it the Trends tab with the weekly lead time, benchmark zones and markers for a new CI pipeline and the AI rollout

Four metrics in one gadget

Deployment frequency, lead time for changes, change failure rate and time to restore for the last 30 days, 90 days, 6 months or 12 months. The Trends tab shows each one week by week or month by month.

  • An Elite, High, Medium or Low band from the published DORA™ research.
  • An arrow against the previous period of the same length, and one sentence in plain language.
  • ⓘ explains how each number is calculated. Details lists what was left out.
More in the docs →
Video

Watch the tour

A short walkthrough of DevOps Metrics in Jira.

Why the app

Jira alone vs. with DevOps Metrics

Jira aloneWith DevOps Metrics
Deployment frequencyA report that needs deployment data from a connected CI/CD toolCounted from Jira releases, or from issues reaching a status. Nothing to connect
Change failure rate and time to restoreNot among the built-in reports of Jira SoftwareFrom bugs raised within 14 days of a release (without releases: reopened issues), and from incident tickets
Effect of an AI rolloutNo built-in before/after viewTwo equally long periods before and after the rollout date, on all four metrics (Pro)

Compared with Jira Cloud without apps. Jira's own deployment frequency report is described on Atlassian Support.

Plans

Free and Pro

Sites with up to 10 users pay nothing for the app. Larger sites start with a free trial; per-user pricing is on the Marketplace listing.

Free

Without an active subscription, for example after the trial

  • Overview gadget for one project
  • All four metrics with bands, arrows and sentences
  • Trends, weekly or monthly, with benchmark zones
  • Deployments as releases or as issues reaching a status
  • Data-quality footnote and Details

Pro

During the free trial and with a subscription

  • Everything in Free
  • Up to 10 projects combined in one gadget
  • AI Impact tab and the AI rollout step
  • Advanced: incident types and sub-tasks
  • Up to five event markers on the trend chart
  • DevOps Metric Card gadget
  • PNG, CSV and Copy as text exports
Setup

Running in three steps

1

Install

Get the app from the Atlassian Marketplace and confirm the installation on your Jira site.

2

Add the gadget

On a Jira dashboard, choose Add gadget, search for “DevOps Metrics” and add DevOps Metrics — Overview.

3

Pick a project

Accept the recommended deployment setting. The first analysis fills the tiles, usually in about a minute.

FAQ

Common questions

More answers in the documentation, or write to support@janekbehrens.de.

How can it measure DORA™ metrics without CI/CD data?
From the Jira data you already have: released versions or status changes for deployments, the first “In progress” to the last “Done” for lead time, bugs raised within 14 days of a release (without releases: issues moved back out of Done) for the change failure rate, and incident tickets from created to resolved for time to restore. These are approximations from work items, measured the same way every time. The ⓘ on every tile says how the number is calculated.
What counts as a deployment?
You choose in the setup wizard: Jira versions marked as released (with a release date), or issues that first reach statuses you pick. With at least three releases in the last 90 days the wizard recommends releases, otherwise the status option. Both options are in Free.
Can it show whether our AI rollout changed delivery?
Yes, with Pro. Enter the rollout date in step 3 of the wizard. The AI Impact tab compares two equally long periods before and after it on all four metrics, with a rule-based verdict, and compares AI-involved issues with the rest. AI involvement comes from labels, issue types and app-account activity. Results are team totals, never per person.
How up to date are the numbers?
The first analysis reads up to 12 months of completed issues once. After that the data is refreshed every night for projects opened in the last 45 days, and the refresh button updates a project right away, at most once every 10 minutes. Jira reloads the gadgets every 3 hours.
Does the app change my issues or store personal data?
No. The app only reads Jira work data and never writes to your issues. It stores weekly aggregate numbers in Atlassian's Forge storage: no names and no account IDs. Details in the Trust Center.
Is it free?
Jira sites with up to 10 users pay nothing. Larger sites start with a free trial. Pro features are on while the site has an active subscription, the trial included. Without one, for example after the trial, the Overview gadget keeps working for one project with all four metrics, bands and trends.

Delivery numbers your whole team can read

Free for Jira sites with up to 10 users. Larger sites start with a free trial.