Building a Jira Dashboard That Actually Tells You Something
Most Jira dashboards are abandoned within a month. Someone sets up a few gadgets, shares the link in Slack, and moves on. Two sprints later nobody opens it, because the numbers don't mean anything or the gadgets are always stale.
The problem isn't Jira. Dashboards tend to get built around what's easy to show rather than the decisions they're supposed to support.
This post covers how to think about Jira dashboards, which metrics matter, which Jira features give you each one, and how to add charts your team will check every day.
What makes a dashboard useless
Most bad Jira dashboards share a few traits:
Too many gadgets. A dashboard with 12 gadgets isn't four times as useful as one with three. It's less useful, because nothing stands out.
Wrong time horizon. A sprint burndown that resets every two weeks won't help you plan the quarter, and one sprint of velocity isn't a trend. Match each gadget to the time horizon of the question you're asking.
Metrics that measure activity, not outcomes. "Issues created this week" tells you the team is logging tickets. It doesn't tell you whether the project is on track. Issues completed against what was committed is a more honest number.
No audience. A standup dashboard looks nothing like an exec review dashboard. Mixing the two produces something mediocre for both.
The metrics that matter, and where to find them
Here are five metrics worth tracking for most software teams, and the Jira feature that gives you each one.
Sprint burndown
Are you on track to finish the sprint commitment? A healthy burndown slopes steadily toward zero. A flat line mid-sprint means work isn't getting closed. A cliff on the last day means work wasn't broken down well.
Where: Jira's built-in Sprint Burndown gadget on the dashboard, or the burndown chart in your board's Reports.
Velocity over several sprints
Velocity (story points or issues completed per sprint) is useful when you look at four to eight sprints. One sprint is noise; a rolling view is a planning input. Big swings usually point to estimation drift, unplanned work, or scope changes worth raising in the retro.
Where: the Velocity chart in your board's Reports (Scrum boards in company-managed projects).
Cycle time
How long does an issue take from "In Progress" to "Done"? High cycle times for small issues usually point to blockers, review bottlenecks or unclear acceptance criteria. High variance means the process is inconsistent.
Where: the Control chart or cycle time report in your board's Reports, or the Average Time in Status dashboard gadget.
Blocked issues by assignee
How many blocked issues does each person have? If one person has five and everyone else has none, that's a structural problem, not an individual one. Put it on the standup dashboard so blockers get seen early.
Where: a bar chart in Charts for Jira (setup below), or Jira's Filter Results gadget pointed at a "blocked" filter.
Issues without an assignee
Work that's been created but not picked up. During a sprint this number should be low. When it climbs mid-sprint, scope has usually crept in through the side door.
Where: a Charts for Jira chart or a Filter Results gadget using assignee is EMPTY.
Adding charts with Charts for Jira
Charts - Reports and Graphs for Jira Dashboard is a free gadget, built on Atlassian Forge, for charting your current issues on any Jira Cloud dashboard. It offers bar, line, pie, area and scatter charts plus tables. It doesn't replace Jira's agile reports (burndown, velocity, control chart). It covers the distribution and workload views those reports don't.
Adding a chart gadget
- Open your Jira dashboard and click Edit.
- Click Add gadget and search for "Charts - Reports and Graphs".
- Choose your data source: one or more projects, fields, labels, or a saved filter.
- Optionally add a JQL query to narrow the issues further.
- Pick a chart type.
- Choose how to group the data: status, assignee, issue type, project, labels or priority.
- Add a title and colors, then save.
The chart reads from your Jira site, so it reflects the current state of your issues. The quick start guide covers each step.
Grouping options worth knowing
Group by status shows how many issues sit in each workflow state. It's good for spotting pileups: ten issues in "In Review" and two in "Done" means review is the bottleneck.
Group by assignee shows workload. Scope it to the current sprint with JQL and you can see at a glance whether load is balanced.
Group by labels helps teams that run several workstreams in one sprint. If you label work by area, you can see how effort is split.
Group by project with the project comparison mode puts several teams or products side by side, which is useful for managers who look after more than one project.
Three dashboard layouts for different audiences
Standup dashboard
Audience: the team. Time horizon: current sprint.
| Gadget | What it shows |
|---|---|
| Sprint Burndown (built-in) | Are we on track? |
| Blocked issues by assignee (Charts for Jira, bar) | What needs unblocking? |
| Current sprint issues by status (Charts for Jira, bar) | Where is work piling up? |
| Unassigned issues (Filter Results) | What hasn't been picked up? |
Keep this to four gadgets. The goal is a 60-second read before standup.
Exec and stakeholder dashboard
Audience: non-engineering leadership. Time horizon: current quarter.
| Gadget | What it shows |
|---|---|
| Created vs Resolved (built-in) | Is incoming work outpacing delivery? |
| Release issues by status (Charts for Jira, stacked bar scoped by fix version) | Are we on track for the release? |
| Open issues by priority (Charts for Jira, pie or bar) | What's the risk surface? |
| Road Map (built-in) | Upcoming versions and their progress |
Avoid sprint-level detail here. Leadership wants quarter-level signal. Link to the Velocity chart if someone asks about throughput.
Retrospective view
Audience: the team. Time horizon: the sprint that just ended.
For retros, Jira's board reports do most of the work: the sprint report and burndown chart for the completed sprint, the Velocity chart for the trend, and the control chart for cycle time. Add a Charts for Jira chart of issues that carried over, using JQL such as project = MYPROJ AND sprint in closedSprints() AND sprint in openSprints() (issues that sat in an earlier sprint and are still in the current one), grouped by assignee or issue type.
A note on JQL
JQL is optional in Charts for Jira (you can chart a whole project or label), but a few patterns make scoping much faster:
-- Current sprint, this project
project = MYPROJ AND sprint in openSprints()
-- Blocked issues
project = MYPROJ AND status = "Blocked"
-- Issues completed in the last 30 days
project = MYPROJ AND statusCategory = Done AND resolved >= -30d
-- High priority, unassigned
project = MYPROJ AND priority = High AND assignee is EMPTY
Save the ones you use most as Jira filters, then select the saved filter when configuring gadgets instead of retyping JQL. The same saved filters work in Jira's built-in gadgets too.
Getting started
Install Charts - Reports and Graphs for Jira Dashboard from the Atlassian Marketplace. It's free, built on Forge, and works on Jira Cloud. Full documentation is at /docs/charts-for-jira-dashboard.
For a rundown of which built-in gadgets to use, see Best Jira Dashboard Widgets and Charts in 2026. For step-by-step chart setups, see How to Track Jira Issues with Charts and Graphs.
Questions? Reach out via our support portal.
