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:

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:

  1. project = OPS AND statusCategory = "In Progress" saved as OPS in progress
  2. project = OPS AND statusCategory != Done AND duedate < now() saved as OPS overdue
  3. project = OPS AND statusCategory != Done AND updated < -7d saved as OPS untouched for a week

Then add:

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.

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?

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?

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?

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.

  1. Give every routine ticket the same label, for example routine.
  2. Save project = OPS AND labels = routine AND statusCategory != Done as Routine work open.
  3. Save project = OPS AND labels = routine AND statusCategory != Done AND duedate < now() as Routine work overdue.
  4. Save project = OPS AND labels = routine AND created >= startOfMonth() as Routine work this month.

Then add:

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:

Whichever you choose, the dashboard reads the same: one label, three filters, three gadgets.

Tips that apply to every example #

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.