Questions

No. Inside Jira, no servers. Changeline runs on Atlassian Forge, reads Jira as you and changes nothing in it. Nothing is sent anywhere.

No. This is DORA the delivery metrics: deployment frequency, change lead time, failed deployment recovery time, change fail rate and deployment rework rate. It is not the EU’s Digital Operational Resilience Act. DORA is a research programme at Google and a trademark of Google LLC; Changeline is not made or endorsed by Google.

Not yet: Changeline is not on the Atlassian Marketplace. Leave your email for one message the day it is live.

The five figures for the space’s released versions of the last 90 days. Changeline reads the versions and bugs your Jira already holds, so the first page it opens has numbers, with nothing to connect and nothing to set up first.

Yes. The Changeline panel, from View app actions under the work item’s title, shows its change lead time and the three stages with bars, the release it shipped in and whether that release failed, and the Details column holds a glance. A failure shows the release it points at and how long it took to recover.

No. A deployment is a released version in Jira, or, if you keep no versions, a work item that reaches Done. Deployments a CI/CD tool sends to Jira are not read.

Only from deployments a connected CI/CD tool sends to Jira, mapped to a Production environment, and it shows no change fail rate, no failed deployment recovery time and no deployment rework rate. Changeline counts all five from the versions and bugs your teams already keep.

No. It reads Jira as you and writes nothing back, to a work item or to a setting.

Free up to 10 users, then billed per user by Atlassian, with a 30-day free trial. Every feature is on the free tier. The price per user drops as you grow, and the Marketplace listing shows the exact cost for your site.

By default as a released version: a version marked Released with its release date in the period. If your teams ship without versions, a Jira admin can count each work item that reaches Done instead. The choice is made once for the site.

For each work item deployed in the period, from its first move out of a To Do status to its release, at the end of the release day, or to Done. A work item never seen leaving To Do starts at its creation. The figure is the median. DORA starts the clock at the commit, but Jira gives an app no commit times, so work starting is the nearest. A Jira Automation rule, “Branch created → move to In Progress” (GitHub, GitLab or Bitbucket for Jira), makes the two the same. A Jira admin can start every work item at its creation instead.

Yes. Under the five figures, Where the lead time goes splits it into waiting to start, in progress and waiting for release, each a median, and names the largest. The Releases tab gives the three for each release.

A work item of a failure type that points at a release: its Affects versions names it, or it links to a work item of that release. Bug is a failure type by default, and so is every work type whose name contains “Incident”. A release with one such failure or more failed. Change fail rate is the failed releases out of all releases. A Jira admin chooses the types, and can add spaces to read failures from, such as a Jira Service Management space.

The median time from a failure’s creation to the release that ships its fix, named in its Fix versions, else to its Done. It is a work item’s life in Jira, not an outage’s start to its end. A failure not yet recovered is listed apart, and joins the figure when it is.

The share of releases that ship a fix for a production failure: a release named in the Fix versions of a failure that points at an earlier release. DORA added it beside change fail rate, as the second measure of instability.

Yes, against your own past. Each figure carries a lozenge: green when it is better, red when it is worse, set against the same number of days just before the period, such as “18% faster” or “4 points lower”. Its count line shows the figure before, such as “3 of 8 releases · was 50%”. Where there is nothing to compare, none is drawn. Changeline shows no bands and no ranking against other teams: DORA’s 2025 report dropped them, and says a team improves against its own past.

Yes. A space’s own tab counts that space. Under Apps, pick spaces, a saved filter or a JQL, and the figures count only those work items and the releases that hold them. With more than one space, a Spaces tab sets each space’s five figures side by side. Copy link shares the view.

No. Every figure is a team’s. Changeline reads no assignee or reporter and shows no person’s name in a figure. The one name it reads is each saved filter’s owner’s, only to tell apart two filters with one name, and it is never stored.

A page is kept for an hour, per person, scope and period, a work item’s panel for ten minutes, so they open at once, and Recalculate reads them again. A read of more than 5,000 work items stops and says to pick fewer spaces or a shorter period.

Jira administrators, under Jira settings › Apps › Changeline settings. Everyone else sees the figures for the work items they may browse.

Its settings, an hour’s cache of the figures and the rows they were counted from, ten minutes’ cache of a work item’s panel, the site’s work types for an hour, each person’s remembered scope, the card’s dismissal and the review request’s count. It stores no person’s name and writes nothing to Jira.

Spaces, versions, work items with their dates, status changes, links, affected versions, fix versions, work types and saved filters (read:jira-work), and its own storage (storage:app). Nothing else: no assignee, no reporter and no write permission.

Ask support first: it may already be a setting. If it is another app, tell us. When other teams need it too, we build it.

Request an app →