Jira Dashboard Setup: the 5 Gadgets Every Engineering Team Needs

Most Jira dashboards die in three weeks. Someone configures 15 gadgets in week 1, no one looks at week 2, the dashboard owner leaves the company by week 4. The fix is the same as for Jira itself: less is more. Five gadgets, each answering one specific question. That's the entire dashboard.

The five gadgets

1. Sprint Burndown (for Scrum) or Cumulative Flow Diagram (for Kanban)

Question it answers: Are we on track for our commitment?

Sprint Burndown plots remaining story points or issue count against time. A healthy burndown trends down toward zero by the sprint end date. A flat line for 3 days mid-sprint = blocker. A spike upward = scope was added (uncommitted work pulled in).

For Kanban teams, use Cumulative Flow Diagram instead. It shows the count of issues in each workflow state over time. A widening band in "In Progress" or "In Review" = WIP is growing, which usually means engineers are starting work faster than they finish it. Symptom of context switching.

Setup: Add Gadget → Sprint Burndown Gadget → pick board → pick sprint (typically "Current Sprint"). For Cumulative Flow: Add Gadget → Created vs Resolved Chart, then add a second gadget showing status counts over time via a Two-Dimensional Filter Stats gadget on a daily filter.

2. Issue Statistics by Assignee

Question it answers: Who's overloaded?

Shows count of open issues per assignee. If one engineer has 12 open tickets and everyone else has 4, you have a load-balancing problem. Either the team isn't picking up new work, or one person is hoarding (often unintentionally), or others are blocked.

Setup: Add Gadget → Issue Statistics → configure the filter (e.g., project = ENG AND status in ("To Do", "In Progress", "In Review")) → group by Assignee. Display as a horizontal bar chart for quick scan.

Pro tip: Add a second copy of this gadget filtered to "In Progress" only. The difference between the two charts tells you who has a backlog vs who has too many things in flight simultaneously.

3. Created vs Resolved Chart

Question it answers: Is the backlog growing faster than we can ship?

Plots issues created per week vs issues resolved per week. If created > resolved for 3+ weeks running, your backlog is growing. Either you need more capacity, or you need to push back on the inflow source (PM, support tickets, etc.).

This is the single most underrated gadget. It's the financial-statements equivalent for engineering throughput. Look at it weekly.

Setup: Add Gadget → Created vs Resolved Chart → Filter: your team's project → Period: Weekly → Days: 90 (to see a quarter at a glance).

4. Recently Updated Issues

Question it answers: What's the team actually working on right now?

A simple list of issues updated in the last 24 hours, sorted by most recent. Comments, status changes, assignment changes, anything counts. This is the "pulse" gadget — it tells you whether the team is active or stuck.

If the list is empty by Wednesday afternoon, something is wrong. Either nobody is working (vacation, conference, all in meetings) or work is happening outside Jira (which means your dashboard reports the wrong reality).

Setup: Add Gadget → Filter Results → create a saved filter updated >= -1d AND project = ENG ORDER BY updated DESC → display columns: Key, Summary, Assignee, Status, Updated.

5. Two-Dimensional Filter Statistics

Question it answers: What's the work distribution across two axes I care about?

The most flexible gadget Jira ships with. Pick a JQL filter, then group by two dimensions. Examples we use constantly:

• Status x Assignee — who has work in each state
• Component x Priority — where the most critical work lives
• Issue Type x Sprint — bug vs feature balance per sprint
• Fix Version x Status — release readiness

Setup: Add Gadget → Two-Dimensional Filter Statistics → pick filter → X-axis dimension → Y-axis dimension → Number of results: 20 (default 10 is too few).

Layout that works

JQL filters to save first

Before adding gadgets, save these filters. Most gadgets need a saved filter as input, and reusing filters is cleaner than duplicating JQL in each gadget config.

• ENG-active: project = ENG AND status in ("In Progress", "In Review") AND resolution = Unresolved
• ENG-backlog: project = ENG AND status = "To Do" AND resolution = Unresolved
• ENG-stale: project = ENG AND status = "To Do" AND updated < -30d
• ENG-this-sprint: project = ENG AND sprint in openSprints()
• ENG-bugs-open: project = ENG AND issuetype = Bug AND resolution = Unresolved

Gadgets to avoid

Sharing the dashboard

Three options:

1. Project-only sharing: Everyone with access to the project sees it. Default and best.
2. Public sharing: Anonymous viewers can see it. Useful for status pages. Be careful with sensitive issue summaries.
3. Logged-in users: Anyone with a Jira license. Use for cross-team visibility (e.g., Product looking at Eng dashboard).

To share with executives without paying for Jira licenses: schedule a weekly export to Confluence. Atlassian's Export Dashboard to PDF + Automation rule that uploads to a Confluence page is the cheapest path.

FAQ

How many gadgets should a Jira dashboard have?
Five to seven max. Each should answer one specific question. If you can't articulate the question in one sentence, remove it.

Why doesn't Sprint Burndown work for Kanban?
Burndown assumes fixed scope and an end date. Kanban has neither. Use Cumulative Flow Diagram or Control Chart instead.

Can I share a dashboard with non-Jira users?
Only via public sharing (anonymous) or by buying viewer licenses. For executive visibility, export to Confluence weekly.

What JQL should I use for 'work in progress'?
status in ('In Progress', 'In Review') AND assignee = currentUser(). For team WIP, swap currentUser() for project + board filter.