Skip to content
Menu

How to build a Jira dashboard for flow metrics

A Jira dashboard for flow metrics combines gadgets such as Average Time in Status, Created vs Resolved, Resolution Time and Average Age on one page. Jira Cloud has no dashboard gadget for the Control chart or the cumulative flow diagram, so cycle time and cumulative flow stay in board reports. Here is a setup that covers throughput, time in status and aging work, and what a Jira dashboard can’t show.

Updated · hey.space by TimeCamp

Create the dashboard

  1. From your Jira space, select Dashboards in the sidebar, then Create dashboard.
  2. Name it (for example “Team flow”), add a description and save. To share it, select More actions (•••) > Rename or share.
  3. Select Edit, then Change layout to pick two or three columns.
  4. Select Add gadget and Add next to each gadget you want. New gadgets appear at the top of the left column.

Any Jira user can create a dashboard (Atlassian: create and edit dashboards, add and customize gadgets). Most gadgets read from a saved filter, so save one first, for example:

project = "WEB" AND type in (Story, Bug) ORDER BY created DESC

Gadgets that show flow metrics

These built-in Jira Cloud gadgets cover the main flow metrics (Atlassian: dashboard gadgets):

GadgetFlow metricWhat it showsWatch for
Average Time in StatusTime in statusAverage days work items spent in each statusCounts resolved work items only
Created vs Resolved ChartThroughput and arrivalsWork items created against work items resolved over timeA growing gap means work piles up
Resolution TimeLead timeAverage days from created to resolvedTotal elapsed time, 24/7; fractions of days are cut off
Average Age ChartWork item ageAverage days that open work items have been unresolvedRising age means old work is not finishing
Average Number of Times in StatusReworkHow often work items return to a statusValues above 1 for In Review point to rework loops
Two Dimensional Filter StatisticsWork in progressA table of a filter’s results by two fields, such as status and assigneeUse with a filter for unresolved work

Average Time in Status counts only work items that are already resolved (Atlassian: JRACLOUD-77733), so it describes finished work. For work still in progress, pair it with Average Age and a Two Dimensional Filter Statistics table of open work by status.

A layout that works

A two-column flow dashboard that answers the questions a weekly team review asks:

  1. Is work finishing? Created vs Resolved Chart, last 90 days, by week.
  2. Where does it wait? Average Time in Status for the same filter.
  3. How long does it take? Resolution Time, last 90 days.
  4. Is old work stuck? Average Age Chart, and a Filter Results gadget for resolution = Unresolved AND updated <= -14d.
  5. Where is work in progress now? Two Dimensional Filter Statistics with status by assignee or by type.
  6. Is there rework? Average Number of Times in Status.

Cycle time and cumulative flow live in board reports

The Cloud gadget list has no Control chart, cumulative flow or cycle time gadget. Keep these board reports open next to the dashboard:

Example: what the dashboard told one team

An example of reading the dashboard together for a team of eight engineers:

GadgetLast monthThis month
Resolved work items4639
Average time in In Review1.6 days3.4 days
Average age of open work items9 days14 days
Average times in In Review1.21.7

Example data. Fewer work items finished, review time doubled and work items went back to review more often. The dashboard shows where the flow slowed down, but not why: whether reviewers were busy elsewhere, waiting for builds or answering support escalations.

What a Jira dashboard can’t show

Built-in gadgets read Jira data from one site and cannot combine several data sources in one chart (Atlassian: gadgets). Time spent outside Jira, in the IDE, in code review tools, in Slack or in a helpdesk, never reaches the dashboard, and neither does the switching between them.

When you need an engineering management platform

An engineering management platform adds what Jira dashboards miss: data from Git, CI and chat next to Jira, and trends across teams. If your question is where engineering time actually goes and which handoffs to automate, hey.space covers it from activity data. It imports Jira, GitHub, GitLab and Azure DevOps work as tasks and matches the team’s activity to it, so you see time per work item, the switching between tools and the repeated steps worth automating. See how hey.space finds automation opportunities, the sample report and the integrations.

See where your engineering flow slows down

Start with a 30-minute call. A 2-week pilot shows time in status, queues and the work that happens outside Jira, with what to change first.

30-minute call. We’ll show what a 2-week pilot on your team’s data would reveal.