By Yamuno Team
07 May 2026
6 min read
Most Jira dashboards are abandoned within a month of being created. They start with good intentions — someone sets up a few gadgets, shares the link in Slack, and declares victory. Two sprints later, nobody opens it because the numbers don't mean anything or the widgets are always stale.
The problem isn't Jira. It's that dashboards get built around what's easy to surface rather than what decisions they're supposed to support.
This post covers how to think about Jira dashboards, what metrics actually matter, and how to set up charts that a real team will check daily.
Before getting into what works, it's worth naming the failure modes. Most bad Jira dashboards share a few characteristics:
Too many widgets. A dashboard with 12 gadgets isn't 4x as useful as one with 3 — it's less useful because nothing stands out. If everything is visible, nothing is.
Wrong time horizon. A sprint burndown chart that resets every two weeks doesn't help you plan the quarter. A velocity trend over one sprint isn't a trend. Match the widget to the time horizon of the question you're asking.
Metrics that measure activity, not outcomes. "Issues created this week" tells you your team is logging tickets. It doesn't tell you whether the project is on track. Issues closed vs committed is a more honest number.
No audience. A dashboard built for standup looks completely different from one built for an exec review. Mixing those purposes produces something that's mediocre for both.
Here are the five metrics worth tracking for most software teams, and why:
The most immediate signal. Are you on track to complete your sprint commitment? A healthy burndown slopes steadily toward zero. A flat line mid-sprint means work isn't getting closed. A cliff at the end means scope wasn't broken down properly.
Track it per sprint. The shape matters as much as the final number.
Sprint velocity — story points or issue count completed per sprint — is useful when you look at it over 4–8 sprints. A single sprint's velocity is noise. A rolling average is a planning input.
Watch for velocity swings greater than ±30% — those usually point to estimation drift, unplanned work, or sprint scope changes worth discussing in retrospectives.
How long does an issue take from "In Progress" to "Done"? Cycle time is one of the most diagnostic metrics in software delivery. High cycle times for small issues usually indicate blockers, review bottlenecks, or unclear acceptance criteria. High variance means your process is inconsistent.
This is the metric most teams skip and then wonder why estimates are always wrong.
How many blocked issues does each person have? This is a team health metric disguised as a workload metric. If one person has 5 blocked issues and everyone else has zero, that's a structural problem — not an individual one.
Surface this in your standup dashboard so blockers get visibility before they become incidents.
Work that's been created but not picked up. In a healthy sprint this number should be low. In a backlog it's expected. When it climbs during a sprint, it usually means scope crept in through the side door.
Charts - Reports and Graphs for Jira Dashboard is a Forge-native gadget that adds a proper charting layer to Jira dashboards. It supports bar charts, line charts, pie charts, and burndown-style visualizations — all configured directly in the dashboard without needing external tools or BI integrations.
The gadget renders immediately and stays live — data updates automatically as issues change.
Group by status gives you a distribution view — how many issues are in each workflow state. Useful for spotting pileups (10 issues in "In Review," 2 in "Done" — something's blocking review).
Group by assignee shows workload distribution. Combine with a filter for a specific sprint and you can see at a glance if load is balanced.
Group by label or component is useful for teams that run mixed-project sprints — you can see how effort is distributed across workstreams.
Group by sprint over multiple sprints gives you the velocity trend you need for planning conversations.
Audience: the team. Time horizon: current sprint.
| Widget | What It Shows |
|---|---|
| Sprint burndown | Are we on track? |
| Blocked issues by assignee | What needs unblocking? |
| Issues in each status | Where is work piling up? |
| Issues without assignees | What hasn't been picked up? |
Keep this to 4 widgets maximum. The goal is a 60-second read at 9am.
Audience: non-engineering leadership. Time horizon: current quarter.
| Widget | What It Shows |
|---|---|
| Velocity trend (rolling 6 sprints) | Is the team's throughput stable? |
| Epic progress (% complete) | Are we hitting roadmap milestones? |
| Issues by priority (open) | What's the risk surface? |
| Releases completed this quarter | Shipping cadence |
Avoid sprint-level detail here. Execs want quarter-level signal, not sprint noise.
Audience: the team. Time horizon: completed sprint.
| Widget | What It Shows |
|---|---|
| Sprint burndown (completed sprint) | Did we hit the commitment? |
| Cycle time distribution | Were estimates accurate? |
| Unresolved issues carried over | What spilled? |
| Velocity vs previous sprint | Did throughput improve? |
This dashboard exists to feed the retro conversation, not to survive past it. Create it, run the retro, archive it.
Every chart in Charts for Jira is backed by a JQL filter. Learning a few patterns makes dashboard configuration much faster:
-- Current sprint, this project
project = MYPROJ AND sprint in openSprints()
-- Blocked issues
project = MYPROJ AND status = "Blocked"
-- Issues completed in last 30 days
project = MYPROJ AND status = Done AND resolutiondate >= -30d
-- High priority, unassigned
project = MYPROJ AND priority = High AND assignee is EMPTY
Save your most-used filters in Jira's filter management — then reference them by name when configuring gadgets rather than re-entering JQL each time.
Install Charts - Reports and Graphs for Jira Dashboard from the Atlassian Marketplace. It's Forge-native and works on Jira Cloud.
Full documentation is at /docs/charts-for-jira-dashboard.
Questions? Reach out via our support portal.
Featured App
Visualize Jira issues with interactive, customizable charts and tables
Get product updates and tips straight to your inbox.
No spam, ever.
Use Confluence as your team's editing surface and Git as the source of truth. Here's how to export Confluence pages to structured Markdown files that slot directly into a docs-as-code pipeline.
Read more
Confluence doesn't render markdown natively — paste it in and your formatting disappears. Here's how to write markdown directly inside Confluence pages and have it render perfectly.
Read more
We're proud to share that Yamuno has been named a finalist for the Atlassian Partner of the Year 2026: Marketplace Rising Star Award. Here's what this recognition means to us and the community that made it possible.
Read more