How to Build a Sprint Health Dashboard in Jira

The problem with Jira's default sprint view

Jira's sprint board tells you one thing: which column each ticket is in. To Do, In Progress, Done. That's useful — but it isn't sprint health. An issue marked "In Progress" could be hours from done or just starting. You can't tell from the label.

The built-in Sprint Report focuses on story points completed vs remaining. That tells you how much work has left the sprint, not how far along the remaining work is. On day nine of a two-week sprint, knowing that four tickets are "In Progress" is very different from knowing they're each at 80% — or each at 10%.

What sprint health actually means

A healthy sprint has three properties:

• In-progress items are advancing. Not just labeled "In Progress" by status, but genuinely moving forward day over day.
• No hidden blockers. An issue that has been "In Progress" for six days without movement is a risk signal — whether or not it has a formal blocker tag.
• The overall completion rate is on track. If the sprint has ten stories and it's day eight of ten, an average progress below 70% warrants a conversation.

None of these are visible in Jira's default views. You need progress information at the issue level, not just at the status level.

Progress bars: the missing layer

Adding a progress bar custom field gives each issue a color-coded bar and a percentage. That percentage can come from one of three sources:

• Status-based: automatically maps each workflow status to a percentage. When someone moves a ticket from "In Progress" to "In Review", the bar advances from 50% to 75% with no extra clicks. You configure the mapping once in Admin Settings.
• Subtask-based: calculates resolved subtasks ÷ total subtasks. Useful for stories with detailed acceptance criteria broken into child issues.
• Manual: the assignee sets the percentage themselves using a slider or quick-select buttons (0%, 25%, 50%, 75%, 100%). Useful for tasks where status alone does not capture complexity.

The color coding is configurable: red below 34%, yellow up to 67%, green above — or whatever thresholds fit your team's definition of "at risk". The same thresholds apply everywhere the field appears: the issue view, the list view column, and the dashboard.

Sprint health in the list view

Once a progress bar field exists, add it as a column to your Jira list view or backlog. During standup, open the list view and sort by progress ascending. The lowest-progress in-progress items surface at the top — those are the tickets that need a conversation.

A sprint full of yellow and green bars on day three looks very different from one full of red on day nine. That difference is visible in a glance rather than buried in a report.

Progress bar column in the Jira list view — sort ascending to bring at-risk items to the top

The dashboard gadget: a sprint-level overview

The Visual Progress Tracker dashboard gadget — called Progress Tracker Overview — gives you a table of all issues in a project, each with a progress bar, plus an overall average completion percentage at the top.

To scope it to your active sprint, use the optional JQL filter when configuring the gadget. Enter sprint in openSprints() to show only issues in the current sprint. Combine it with type = Story if you only want stories, not sub-tasks.

The table shows each issue's key, summary, type, status, and a progress bar. Any column is sortable — clicking the Progress header lets you rank issues by completion. The average at the top gives you a single number: how done is this sprint right now.

The gadget caches data for up to one hour to keep Jira API usage low. A Refresh button and a "X minutes ago" indicator give you control over when it updates.

The Progress Tracker Overview gadget on a Jira Dashboard — sprint average at top, all issues listed with color-coded progress bars

Setting it up

1. 1
   Install Visual Progress Tracker from the Atlassian Marketplace. Free trial available, no credit card required.
2. 2
   Create a progress bar field. Go to Jira Settings → Work items → Fields → Create field. Choose "Progress Bar (Status)" for automatic updates based on workflow movement.
3. 3
   Configure status mappings. In App Settings → Status Mapping, assign a percentage to each workflow status — for example: In Progress → 50%, In Review → 75%, Done → 100%. A default mapping is pre-loaded as a starting point.
4. 4
   Add the field to your project screen. Go to Project Settings → Screens → Edit screen and add the progress field. The bar now appears on every issue.
5. 5
   Add the field as a list view column. In any Jira list view or backlog, click the column header area and add the progress bar field.
6. 6
   Add the gadget to a Jira Dashboard. Click Add gadget, search for "Progress Tracker Overview", select your project, and optionally enter sprint in openSprints() as the JQL filter to scope it to the active sprint.

That's the full setup. Once configured, the progress bars update automatically on every status change — no manual maintenance needed.

Frequently asked questions