How to Set Up Jira Dashboards for Sprint Tracking and Stakeholder Visibility
Jira dashboards provide real-time visibility into sprint health, velocity trends, and team performance. Configure gadgets, create JQL filters, and share dashboards with stakeholders.
- How to create and configure a Jira dashboard from scratch
- Which gadgets track sprint health vs long-term trends
- How to set up JQL filters for custom dashboard views
- How to share dashboards and set up email subscriptions
A well-designed Jira dashboard gives your team instant visibility into sprint health, backlog status, and delivery trends. But most dashboards are either empty defaults or cluttered messes that nobody uses.
This guide covers how to build dashboards that actually provide value — from sprint tracking to stakeholder reporting.
Why Dashboards Matter
Without a dashboard, teams rely on manual status updates, Excel spreadsheets, and hallway conversations to understand project health. This is slow, error-prone, and does not scale.
Benefits of a well-designed dashboard:
- Real-time sprint health (no more asking "are we on track?")
- Velocity trends for better future planning
- Stakeholder visibility without constant meetings
- Early warning signs when sprints go off track
- Historical data for process improvement
How to Set Up a Jira Dashboard: Step-by-Step
1. Create a New Dashboard
- Go to Dashboards > Create dashboard
- Name it descriptively (e.g., "Team Alpha - Sprint Dashboard")
- Set the owner (usually the scrum master or team lead)
- Configure sharing:
- Private — only you can see it
- Group — share with a Jira group (e.g., "Engineering Team")
- Project — share with everyone in a project
- Everyone — public dashboard
Recommended: Start private, share with your team, then expand to stakeholders as needed.
2. Add Sprint Health Gadgets
These gadgets show real-time sprint status:
Sprint Health Gadget:
- Shows open vs done issues in the current sprint
- Color-coded by issue type
- Updates automatically as issues move
Sprint Burndown Gadget:
- Tracks remaining work against ideal burndown
- Flat line = blocked work
- Steep drop = work not truly done
Sprint Cumulative Flow Gadget:
- Shows work moving through statuses over time
- Identifies bottlenecks (when bands widen)
- Tracks scope creep (when top band grows)
Configuration:
- Click Add gadget on your dashboard
- Search for the gadget name
- Select your board and sprint
- Set refresh interval (5 minutes for active sprints)
3. Add Velocity and Reporting Gadgets
These gadgets show long-term trends:
Velocity Chart Gadget:
- Shows completed story points per sprint
- Use for capacity planning (average of last 5 sprints)
- Compare committed vs completed
Version Report Gadget:
- Tracks progress toward a release
- Shows estimated completion date
- Identifies scope changes affecting the release
Created vs Resolved Gadget:
- Compares new issues created vs issues resolved
- Growing gap = backlog expanding faster than delivery
- Shrinking gap = team is catching up
Configuration:
- Add the gadget to your dashboard
- Select the project and time range
- Choose the metric (story points, issue count)
- Set the date range (last 5 sprints for velocity, last 30 days for created vs resolved)
4. Configure Filter-Based Gadgets
For custom views, create JQL filters and use them in gadgets:
Useful filters to create:
| Filter Name | JQL | Use Case |
|---|---|---|
| My Open Issues | assignee = currentUser() AND status != Done | Personal task list |
| Blockers | priority = Blocker AND status != Done | Escalation tracking |
| Unestimated Stories | issuetype = Story AND cf[10002] IS EMPTY | Backlog grooming |
| Ready for QA | status = "In Review" AND assignee != currentUser() | QA workload |
| Aging Issues | updated ≤ -7d AND status != Done | Stale work identification |
Gadgets that use filters:
- Filter Results — tabular view of matching issues
- Two Dimensional Statistics — group by two fields (e.g., assignee × status)
- Pie Chart — distribution by a field (e.g., issues by priority)
- Bar Chart — comparison by a field (e.g., issues by assignee)
5. Share and Subscribe to Dashboards
Sharing:
- Share with your team's Jira group for sprint tracking
- Share with stakeholders for visibility
- Use "View as" to preview what others see
Email subscriptions:
- Go to your saved filter (not the dashboard)
- Click Details > New Subscription
- Set frequency: daily, weekly, or custom
- Add recipients (Jira users or email addresses)
- Jira emails a snapshot of matching issues on schedule
Pro tip: Create a "Stakeholder Summary" dashboard with high-level gadgets (velocity, burndown, release progress) and subscribe stakeholders to a weekly email. They get visibility without logging into Jira.
FAQ
How many gadgets should a Jira dashboard have?
Aim for 6-10 gadgets per dashboard. Too many gadgets slow loading and overwhelm viewers. Group related gadgets logically: sprint health at the top, velocity trends in the middle, stakeholder summary at the bottom.
What is the best gadget for tracking sprint progress?
The Sprint Health gadget gives a real-time overview of open vs done issues. Pair it with the Sprint Burndown gadget to see if the team is on track. For longer trends, add the Sprint Cumulative Flow gadget.
Can I share a Jira dashboard with non-Jira users?
Not directly. Non-Jira users cannot view dashboards. Workaround: export dashboard data to a Confluence page or use a reporting tool that integrates with Jira API to generate shareable reports.
How do I create a JQL filter for a dashboard gadget?
Go to Issues > Advanced Search, write your JQL query, save it as a filter, then use that filter in any gadget that supports filter input. Saved filters can be shared with other users.
Can I automate Jira dashboard emails?
Yes. Go to your saved filter > Details > New Subscription. Set the frequency (daily, weekly), add recipients, and Jira will email a snapshot of matching issues on schedule. This works for any saved filter, not just dashboards.