Short definition
A Jira dashboard is a personal or shared landing page made up of gadgets - small widgets that visualize filter results, sprint progress, assigned issues, or charts. Dashboards are owned, share-scoped, and built on top of one or more saved filters. They're the standard way teams expose Jira data to non-Jira-power-users.
Dashboards vs. reports
Reports (Sprint Report, Velocity Chart, Burndown, Cumulative Flow Diagram) are pre-built, board-scoped visualisations of agile data. Dashboards are user-built collections of arbitrary gadgets that can pull from any filter the user has access to. The two are complementary: reports for sprint retrospectives, dashboards for ongoing visibility.
Common dashboard patterns
A few patterns that recur across most Jira instances:
- Team standup dashboard - one gadget per team member (“Assigned to X, in progress”), plus a sprint health gadget. Used in the morning standup.
- Release readiness dashboard - a Created vs. Resolved gadget for the release version, plus a Filter
Results gadget listing open issues with the release’s
fixVersion, plus a Two Dimensional Filter Statistics gadget breaking issues down by component vs. status. - Executive summary dashboard - one big number gadget per KPI (open P0 bugs, customer-reported escapes this sprint, releases shipped this month). Shareable as a public link.
- Personal “my work” dashboard - Assigned to Me, Activity Stream, watched issues, recent filters.
Wallboards
A “wallboard” is a dashboard mode designed for big-screen display - gadgets rotate, refresh intervals are short, and there’s no left navigation. Useful for team rooms or operations centres. Atlassian provides a basic wallboard mode out of the box, and Marketplace apps add more polished versions.
Performance considerations
Dashboards are query-heavy by definition - every gadget runs at least one filter against the issue index on load and on refresh. A few defensive practices:
- Keep gadget counts moderate (under ~12 per dashboard for typical instances).
- Use narrowly-scoped filters -
project = X AND status = Openruns fast; an unboundedassignee = currentUser()across thousands of issues is slow. - Set refresh intervals to the lowest value that the use case actually requires.
- Prefer the Filter Results gadget over the Activity Stream for large filters - Filter Results paginates, Activity Stream re-renders the whole list.
Sharing and embedding
A dashboard’s URL is shareable inside Jira and (with appropriate permissions) externally. For embedding specific gadgets in Confluence, the Jira Issues macro is usually a better fit than embedding a whole dashboard.
Common questions
What is a dashboard in Jira?
A Jira dashboard is a personal or shared landing page made up of gadgets - small widgets that visualize filter results, sprint progress, assigned issues, or charts. Dashboards are owned, share-scoped, and built on top of one or more saved filters. They're the standard way teams expose Jira data to non-Jira-power-users.
What are gadgets in a Jira dashboard?
Gadgets are the visual building blocks of dashboards. Common built-in gadgets: Filter Results, Assigned to Me, Sprint Health, Pie Chart, Two Dimensional Filter Statistics, Created vs. Resolved, Heat Map, and Activity Stream. Marketplace apps add many more. Each gadget is configured independently and most are driven by a filter.
How do you share a Jira dashboard?
Open Dashboard -> tools -> Edit dashboard -> Share, then add scopes (a project, a group, a role, or 'public'). Viewers need both permission to see the dashboard and permission to see the data each gadget queries. Sharing a dashboard doesn't grant access to its underlying filters - those have their own share scopes.
Can dashboards refresh automatically?
Yes. Each gadget has a refresh-interval setting (5, 10, 15, 30 minutes, or never). Useful for wall-display dashboards in team rooms. Be careful with very short intervals across many gadgets - aggressive refresh can put real load on Jira.