Blog ·
Jira dashboard examples: six layouts and the filters behind them
Good Jira dashboard examples all share one habit: each gadget answers a single question, and each one reads from a saved filter rather than from the whole site. Below are six dashboards you can build in Jira Cloud today with the gadgets that ship with it: a team overview, a personal "my work" page, a support queue, a release dashboard, a backlog health check, and a dashboard for the routine work that comes back every week or month. Each one lists the filters to save first, the gadgets to add, and the question it answers.
Statements about Jira's built-in gadgets are as of October 2026, from Atlassian's own documentation.
How a Jira dashboard is put together #
A dashboard is a page of gadgets. You open Dashboards from the sidebar, choose View all dashboards, open or create one, select Edit, then Add gadget. Atlassian's page on adding gadgets describes the wizard: you browse the list and select Add next to each gadget you want, and new gadgets land at the top of the leftmost column.
Three things decide whether a dashboard is useful or ignored:
- The filter under each gadget. Almost every gadget asks for a project or a saved filter. A dashboard built on "the whole project" shows everything, and everything is too much to read in the ten seconds people give it.
- One question per gadget. "What is overdue?" is a gadget. "How is the project going?" is a meeting.
- Who it is shared with. A dashboard nobody else can open is a private bookmark. If you can edit a shared dashboard, everyone with access sees your changes too.
Atlassian is also plain about the limits:
Built-in Jira gadgets have some limitations. They can't display data across multiple Jira instances or combine multiple data sources into a single chart.
For those cases it points to Marketplace reporting apps. Every example below stays inside one site and uses built-in gadgets only.
The gadgets these examples use #
| Gadget | What it shows | Good for |
|---|---|---|
| Filter Results | The issues a filter returns, as a list | Any "what is in this bucket?" question |
| Assigned To Me | Open issues assigned to whoever is viewing | Personal dashboards |
| Created vs Resolved | Created against resolved over a period | Is the queue growing or shrinking? |
| Pie Chart | Issues from a project or filter, grouped by a field | Mix by status, priority, assignee |
| Two Dimensional Filter Statistics | A table of a filter, one field against another | Assignee against status, type against priority |
| Issue Statistics | A filter broken down by one field | Counts per component or label |
| Average Age | Average days issues have stayed unresolved | Spotting a backlog that is going stale |
| Resolution Time | Average days to resolve, per period | How fast support and ops close work |
The descriptions are Atlassian's, trimmed. Your site may list more, including gadgets added by apps you have installed.
Example 1: the team overview dashboard #
Question it answers: what is the team working on, and what is stuck?
Save these filters first:
project = OPS AND statusCategory = "In Progress"saved as OPS in progressproject = OPS AND statusCategory != Done AND duedate < now()saved as OPS overdueproject = OPS AND statusCategory != Done AND updated < -7dsaved as OPS untouched for a week
Then add:
- Two Dimensional Filter Statistics on OPS in progress, assignee down the side and status across the top. One glance shows who holds too much.
- Filter Results on OPS overdue, sorted by due date.
- Filter Results on OPS untouched for a week. This is the list a standup should start from.
- Created vs Resolved on the whole project, over 30 days.
Keep it to four gadgets. A team overview with twelve gadgets is read by its author once.
Example 2: the personal "my work" dashboard #
Question it answers: what should I do next?
This is the dashboard most people should set as their default.
- Assigned To Me, which needs no filter at all because it follows whoever is viewing.
- Filter Results on
assignee = currentUser() AND statusCategory != Done AND duedate <= endOfWeek()saved as Due this week. - Filter Results on
reporter = currentUser() AND statusCategory != Donesaved as Things I asked for, so the requests you raised do not vanish once someone else owns them.
Because the filters use currentUser(), you can share this one dashboard with a whole team and each person sees their own work.
Example 3: the support or request queue dashboard #
Question it answers: is the queue under control?
- Created vs Resolved over 14 days. If the created line sits above the resolved line for a week, the queue is growing.
- Resolution Time for the project. A rising bar is the early warning, long before anyone complains.
- Pie Chart of open requests by priority.
- Filter Results on
project = HELP AND statusCategory != Done AND assignee is EMPTYsaved as Unassigned requests.
If your requests run through Jira Service Management, its queues and SLA reports cover more of this, and the incident management guide shows how the response and the review fit together.
Example 4: the release dashboard #
Question it answers: will this version ship, and what is left?
- Filter Results on
fixVersion = earliestUnreleasedVersion(APP) AND statusCategory != Done. - Pie Chart of the same filter by status, so "nine left, six in review" is obvious.
- Two Dimensional Filter Statistics of the same filter, issue type against assignee, to see whether the remaining work is bugs or features and who holds it.
The release itself still needs its steps done in order. The release checklist guide covers where those steps should live.
Example 5: the backlog health dashboard #
Question it answers: is the backlog rotting?
- Average Age on
project = APP AND statusCategory != Done. A line that keeps climbing means work goes in and never comes out. - Filter Results on
project = APP AND statusCategory = "To Do" AND created < -90dsaved as Older than a quarter. These are the candidates to close. - Issue Statistics on open issues, by component, to find the area that collects untriaged work.
This dashboard pairs well with a regular cleanup. The Jira hygiene guide lists the checks, and the groomed backlog guide shows what the end state looks like.
Example 6: a dashboard for the work that repeats #
Question it answers: did this cycle's routine work actually happen?
Every team has tickets that should come back on a schedule: the monthly access review, the weekly report, patching, the quarterly vendor check, the server certificate renewal. On a dashboard these are easy to lose, because they look like every other ticket. The fix is a label.
- Give every routine ticket the same label, for example
routine. - Save
project = OPS AND labels = routine AND statusCategory != Doneas Routine work open. - Save
project = OPS AND labels = routine AND statusCategory != Done AND duedate < now()as Routine work overdue. - Save
project = OPS AND labels = routine AND created >= startOfMonth()as Routine work this month.
Then add:
- Filter Results on Routine work overdue. This is the gadget that matters: a skipped review shows up here instead of in an audit.
- Pie Chart of Routine work this month by status.
- Created vs Resolved on Routine work open over 90 days, to see whether routine work is being closed as fast as it arrives.
Where the routine tickets come from #
The dashboard can only report the tickets that exist. If somebody has to remember to create the monthly access review, the month they forget is the month the dashboard shows nothing overdue, which looks exactly like a month where everything was done. An empty overdue list is only good news when the tickets were certain to be created.
There are a few ways to make sure they are:
- By hand from a template. Fine for a handful of tickets, as long as one named person owns the calendar. The task template guide covers the options.
- A scheduled Jira Automation rule. Built in, and it can set the label for you. Scheduled rules count toward your automation usage, and the automation pricing guide explains how that is measured.
- A scheduling app. Recurring work items for Jira lets a project administrator write the schedule once inside the project, and each issue is created on time with the fields the rule names, labels included, so every routine ticket arrives already carrying
routineand lands on this dashboard without anyone tagging it. Due dates can be set relative to the run, which is what makes the overdue filter meaningful. The recurring tasks comparison sets the three approaches side by side.
Whichever you choose, the dashboard reads the same: one label, three filters, three gadgets.
Tips that apply to every example #
- Save the filter before the gadget. A gadget built on an unsaved query cannot be shared or reused, and you will rebuild it.
- Name filters after the question. "OPS overdue" beats "Filter 14".
- Set a refresh interval on dashboards left open on a screen. Each gadget has its own setting.
- Duplicate instead of rebuilding. In edit mode, a gadget's More actions menu has Duplicate, which copies the gadget and its configuration.
- Check the fields a chart needs. Atlassian notes that the Workload pie chart reads time tracking fields such as Original estimate, not story points, so it stays empty on a team that only estimates in points.
- Put it on a wall if people stand near one. Jira Cloud can show a dashboard as a wallboard, which suits a support or ops team.
When the built-in gadgets are not enough #
Built-in gadgets cover most team dashboards. Look further when you need a chart that combines several projects' data in ways a single filter cannot express, data from more than one Jira site, or a custom calculated metric. Atlassian's own page points to Marketplace reporting apps for that, and also warns that some third-party gadgets rely on APIs that change over time, so check that an app is maintained before you build a team's main page on it.
For most teams the better first move is fewer gadgets on sharper filters. Start with Example 2 for yourself and Example 1 for the team, add Example 6 once the routine work is labelled, and delete any gadget nobody has looked at in a month.