Jira Cloud
Jira sprint and issue health —
an A–D grade for every issue, sprint and release
The app reads the history already in your Jira work items and grades each one on ten delivery metrics — blocked time, rework, reassignments, open blocking links, sprint carry-over and more. Rovo AI explains the grade and suggests what to do next. Install it, open any work item, pick Delivery Health Check from its app actions, and the grade is there.
Standard edition free for up to 10 users · 30-day trial on every paid plan · no credit card · Jira Cloud · See pricing
The problem
Issue, Sprint & Release Delivery Health Check
Where the work actually slips
None of this is hidden. It is all in the Jira work item history — spread across hundreds of entries that nobody has time to read.
The work looks fine until the last two days. Then the items nobody touched are still in To Do, and there is no time left to do anything about them.
Work quietly moves to the next sprint. Once, twice, four times. Each carry-over looks harmless on its own, and nobody keeps count.
Scope changes after the sprint starts. Items are added and removed mid-flight, and the commitment the team made on day one stops meaning much.
Tickets bounce between development and review. Every return costs time, and no board column shows how often it happens.
Blockers hide in flags and comments. Who flagged it, why, and how long it sat there is in the history — one entry at a time.
Nobody owns the work item. It passes from one assignee to the next, and the work stalls in between.
Work waits more than it moves. A work item can sit for days between active steps, and nothing on the board shows how much of its life was actual work.
Why this app exists
Issue, Sprint & Release Delivery Health Check
Jira shows the work items. It does not tell you which of them are in trouble.
Jira records everything that happens to a work item, but it leaves the reading to you. A timeline of time in status for Jira shows where the days went. This app tells you whether that is a problem — and Rovo tells you what to do about it.
| What you need to know | Jira out of the box | Issue, Sprint & Release Delivery Health Check |
|---|---|---|
| Is this work item healthy? | A days-in-column indicator on the card; the rest is in the history | One A–D grade from ten metrics, with the reason behind each score |
| The sprint at a glance | Sprint Health gadget: time elapsed, work complete, scope change and blockers as sprint-wide percentages | A sprint score built from the health of every work item in it, team workload and impediments (Advanced) |
| Scope change mid-sprint | One percentage for the whole sprint | Flagged on each work item added to or removed from the sprint after it started |
| Carry-over | The Sprint field lists every sprint the work item has been in | Counted per work item: carried over once is a B, two or three times a C, four or more a D |
| Work that bounces back | In the history, one transition at a time | Returns counted per status |
| Blockers | A flag with the comment on the card while it is set | Total blocked time, with the reason given for each flag |
| Dependencies | Work item links | Open blocking links to unfinished work lower the grade |
| Ownership changes | Assignee changes in the history | Reassignments counted and graded |
| Release health | A version’s work items by status on its release page | Progress, forecast and high WIP across every work item in the release (Advanced) |
| What to do about it | Ask Rovo yourself, with no grade to start from | Rovo explains the grade and suggests action items |
What it does
Issue, Sprint & Release Delivery Health Check
Jira work item health, rolled up to sprint and release health
Native Jira work items and their history, graded the same way for everyone on the team.
An A–D grade for every work item
Ten weighted metrics — lead time, cycle time, flow efficiency, blocked time, returns, reassignments, linked work items, due dates, work logged against the estimate and sprint health — roll up into one grade. A metric that does not apply to a work item is left out instead of counting against it.
Sprint health on every work item
Each work item in a sprint is checked against the commitment: still in To Do two days before the sprint ends, added after the sprint started, carried over and how many times, delivered late, or left unfinished when the sprint closed.
Blockers and dependencies
See how long a work item was blocked, with the reason given for each flag, and whether it is waiting on unfinished work through a blocking link. Admins decide which statuses count as blocked.
Rework and ownership changes
Every return to a status the work item has already been in is counted, and so is every change of assignee — two things the board itself never shows.
Status timeline
The work item’s life on one timeline, sized to real time, with flags, worklogs, sprint moves and comments on it — each with the person behind it. A second view adds assignee changes, and you choose which events it shows.
AI insights with Rovo
One click asks Rovo to explain the scores in plain language and suggest action items. Use it when the grade is clear but the fix is not. More on AI in Jira across our apps.
Sprint health on your board and dashboard (Advanced)
One score per sprint, from the health of its work items, team workload and impediments. On your Jira board, it sits above every work item’s grade, filtered by text, JQL, status category, work type or assignee; the dashboard adds each person’s work in progress and groups every sprint by board.
Release and JQL analysis (Advanced)
The same analysis for a whole release, or for any set of work items you can describe in JQL: progress, forecast, high WIP, and an AI summary of blockers with action items to clear them.
How it works
Issue, Sprint & Release Delivery Health Check
From one work item to the whole sprint, in five steps
How a team goes from installing the app to a sprint it can read at a glance — without leaving Jira.
1
Open any work item
Choose Delivery Health Check from the work item’s app actions. The panel shows the overall grade, and you can switch it on for every work item.
2
Read the grade
Drill into each metric to see its score and what pulled the grade down.
3
See where the time went
The status timeline shows every status the work item passed through, who moved it and how often it came back. Reassignments, flags and worklogs are on the same timeline, next to sprint moves and comments.
4
Ask Rovo what to do
Click AI Insights and Rovo explains the scores and suggests action items. When the same pattern shows up on many work items — the board view in Advanced lists them side by side — that is the process step worth fixing.
5
Step back to the sprint, release or JQL query (Advanced)
Open the health view on your board, or the sprint health dashboard, for one score per sprint and every work item behind it — hover over a sprint score for a plain-language explanation — and the same analysis for a release or a JQL query.
The health grade
Issue, Sprint & Release Delivery Health Check
From cycle time to sprint health: ten metrics, one grade
Every work item is read the same way, so a C means the same thing on every team. Here is exactly how.
- Each metric gets A to D. Against the thresholds in the table — nothing hidden in a formula.
- A weighted average makes the grade. Together, the metrics that apply give the work item one letter, A to D.
- What does not apply is left out. A work item that was never in a sprint is not marked down for it.
| Metric | AHealthy | BCaution | CAt risk | DCritical |
|---|---|---|---|---|
| Lead timeCreation to Done, or to today | Under 1 week | 1–2 weeks | 2–4 weeks | 4+ weeks |
| Cycle timeTime in In Progress statuses | Under 24 h | 24–48 h | 48–120 h | 120+ h |
| Flow efficiencyActive share of lead time | 90%+ | 80–90% | 60–80% | Under 60% |
| Blocked timeFlagged or in a blocked status | Under 24 h | 24–36 h | 36–48 h | 48+ h |
| Work log overdueTime logged plus remaining, against the original estimate | Within the estimate, under 95% used | 95% or more of the estimate used | Over the estimate by up to 20% | Over the estimate by 20%+ |
| ReturnsBack to a status it had left | None | 1 | 2–4 | 5+ |
| ReassignmentsAssignee changes after the first | Under 3 | Over 3 | Over 5, or in progress unassigned | Done, never assigned |
| Linked work itemsLinks to unfinished work | None open | Open, not blocking | 1 blocking link | 2+ blocking links |
| Due dateDays to or past the due date; left out if none is set | Done by the due date, or comfortably ahead | Due today and in progress, or due tomorrow and not started | 1 day overdue, or due today and not started | 2+ days overdue |
| Sprint healthThe sprint commitment | Delivered in the sprint | Carried over once, or added mid-sprint | Delivered late, or carried over 2–3 times | Unfinished at sprint close, or carried over 4+ times |
Recognition & numbers
Issue, Sprint & Release Delivery Health Check
Built on Forge, with the Runs on Atlassian badge
Built since 2018 by the team behind release management for Jira — an Atlassian Gold Partner, recognized in Atlassian’s own partner awards, and documented where your security team will look for it.
The app is built on Atlassian Forge and carries the Runs on Atlassian badge on the Marketplace. Our SOC 2 report and security documentation are in the Trust Center.
Atlassian Gold Partner
SOC 2 Type II
10
graded delivery metrics behind every work item’s health grade
5★
average rating across 5 Marketplace reviews of this app
2018
building Jira-native apps, every year since
What teams say
Issue, Sprint & Release Delivery Health Check
What teams say about Issue, Sprint & Release Delivery Health Check
Atlassian Marketplace
★ 5 / 5
“As a Scrum Manager, I’ve always found it tedious to manually dig through ticket histories to find bottlenecks. This app basically does that ‘detective work’ for me.”
Atlassian Marketplace
★ 5 / 5
“The A–D health scoring makes it incredibly easy to scan the board during daily syncs and immediately target tickets that are stuck.”
Atlassian Marketplace
★ 5 / 5
“Simple and actually useful. Helps us quickly see where tasks get stuck”
Editions
Issue, Sprint & Release Delivery Health Check
Start with work item health. Add sprint and release health when you need them.
Two editions, both on Jira Cloud. You can start a free 30-day trial of either one, with no credit card, and change edition at any time, during or after the trial.
- Standard: every work item, graded. The A–D health check on ten metrics, the status timeline, a per-status breakdown of where the time went, and the Rovo AI advisor. Free for sites with up to 10 users.
- Advanced: the whole sprint and the whole release. Everything in Standard, plus sprint, release and JQL analysis — progress, forecast, high WIP and an AI summary of blockers — the health view on your Jira board and the sprint health dashboard. Paid from the first user.
- Jira Cloud only. There is no Data Center version of this app.
| What you get | Standard | Advanced |
|---|---|---|
| A–D health grade on every work item | ✓ | ✓ |
| Status timeline and activity | ✓ | ✓ |
| Per-status breakdown of time spent | ✓ | ✓ |
| AI advisor with Rovo | ✓ | ✓ |
| Sprint-level analysis | — | ✓ |
| Release-level analysis | — | ✓ |
| JQL-based analysis | — | ✓ |
| Health view on your Jira board | — | ✓ |
| Sprint health dashboard | — | ✓ |
| Free for up to 10 users | ✓ | — |
Setup & security
Issue, Sprint & Release Delivery Health Check
Installed from the Marketplace, grading the Jira history you already have
Nothing to import and nothing to configure before the first grade: install it, open any Jira work item and choose Delivery Health Check — the grade opens in the panel on the right.
- A Jira admin installs it from the Atlassian Marketplace. It runs on Jira Cloud. There is no server to stand up and no separate account for your team to create.
- The first grade is one click away. Open any work item, choose Delivery Health Check from its app actions, and switch the panel on for every work item when you are ready — the getting started guide shows where.
- No data to move. Grades are worked out from each work item’s own history — statuses, flags, worklogs, sprints, links and assignees.
- You decide what “blocked” means. Admins choose which statuses count as blocked, and the timeline’s settings decide which events it shows.
- AI needs Rovo. AI insights come from Rovo, so Rovo has to be installed and configured on your site; it is not available on the Free Jira plan. How AI insights work.
- Runs on Atlassian, security documented. Our security posture is in the Trust Center — one link to forward to your reviewer.
- Support from the team that builds it. Questions go straight to our own service desk.
FAQ
Issue, Sprint & Release Delivery Health Check
Jira sprint health — common questions
What is Issue, Sprint & Release Delivery Health Check for Jira?
It is a Jira Cloud app that grades every work item (an issue, in older Jira terms) from A to D on ten delivery metrics — from blocked time and rework to sprint carry-over and open blocking links — so you can see where work is losing time without digging through work item histories. Rovo AI explains each grade and suggests what to do. The Advanced edition rolls the same analysis up to whole sprints, releases and JQL queries.
How is it different from the reports already in Jira?
Jira’s reports show what happened to a sprint or a board as a whole. This app grades every work item A–D on ten metrics and shows which metric pulled the grade down, so the conversation starts from the work items in trouble, not from a chart. Rovo then explains the grade and suggests what to do.
How is the health grade calculated?
Every metric gets a grade from A (healthy) to D (critical). The overall grade is a weighted average of the metrics that apply to the work item, and sprint health carries the highest weight. A metric that does not apply — sprint health for a work item that was never in a sprint, for example — is left out of the average, so it cannot drag the grade down. Every threshold and weight is in the health score metrics documentation.
Does it measure cycle time and lead time in Jira?
Yes. Cycle time is the time a work item spends in In Progress statuses; lead time runs from creation to Done, or to today while the work item is still open. Both are graded A–D — cycle time is an A under 24 hours and a D at 120 hours or more, lead time an A under a week and a D at four weeks or more — and both feed the work item’s overall grade. More on reading these numbers in flow metrics in Jira.
How does it measure sprint health?
On each work item, it checks the sprint commitment. A work item added before the sprint and finished inside it scores well. One added or removed after the sprint started, carried over, delivered late or left unfinished when the sprint closed scores lower, and four or more carry-overs is critical. In the Advanced edition, each sprint also gets its own score, combining the health of its work items, team workload and impediments.
Does it work for Kanban teams that don’t use sprints?
Yes, at work item level. Each work item is still graded on lead time, cycle time, flow efficiency, blocked time, returns, reassignments and linked work items; sprint health is left out for a work item that was never in a sprint, so it cannot pull the grade down. The board view and the sprint health dashboard are built around sprints.
Can it monitor sprint or release health with AI?
Yes, through Rovo. The AI Insights button on a work item asks Rovo to explain the scores and suggest action items, and in the Advanced edition the sprint, release and JQL analysis include an AI summary of blockers with action items to clear them. Rovo has to be installed and configured on your Jira site, so it is not available on the Free Jira plan. More on AI insights.
What is the difference between Standard and Advanced, and what does it cost?
Standard covers every work item: the health grade, the status timeline and the AI advisor. It is free for sites with up to 10 users; above that, it is licensed for the same user tier as your Jira site — that is how the Atlassian Marketplace licenses every app. Advanced adds sprint, release and JQL analysis, the health view on your board and the sprint health dashboard, and is paid from the first user. You can start a free 30-day trial of either edition and change edition at any time. Prices are on the Marketplace pricing page.
Does it work on Jira Data Center?
No. The app is available for Jira Cloud only.
Is it secure?
The app is built on Atlassian Forge and carries the Runs on Atlassian badge on the Atlassian Marketplace. Security, compliance and SOC 2 documentation lives in our Trust Center, which is the single link to send to a security reviewer.
Relevant for you
Issue, Sprint & Release Delivery Health Check
Where teams go next
Not ready for a trial yet — watch the app in a video, read why we built it, follow the setup guide, or start with the Jira sprint report you already have.
Video
Video overview of the app
The video overview of the app from our team, on YouTube.
Article
Finding bottlenecks: the diagnostic routine every delivery manager runs
How a routine of checking flow, blockers and history across every work item became this app — on the Atlassian Community.
Guide
Getting started with the health panel
Switch the panel on, read your first grade and turn it on for every work item, step by step.
Get started
Know which work items are in trouble before the sprint ends
Start a free 30-day trial from the Atlassian Marketplace, or book a walkthrough with our team.
Standard edition free for up to 10 users · 30-day trial on every paid plan · no credit card · Jira Cloud