Create the dashboard
- From your Jira space, select Dashboards in the sidebar, then Create dashboard.
- Name it (for example “Team flow”), add a description and save. To share it, select More actions (•••) > Rename or share.
- Select Edit, then Change layout to pick two or three columns.
- 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 DESCGadgets that show flow metrics
These built-in Jira Cloud gadgets cover the main flow metrics (Atlassian: dashboard gadgets):
| Gadget | Flow metric | What it shows | Watch for |
|---|---|---|---|
| Average Time in Status | Time in status | Average days work items spent in each status | Counts resolved work items only |
| Created vs Resolved Chart | Throughput and arrivals | Work items created against work items resolved over time | A growing gap means work piles up |
| Resolution Time | Lead time | Average days from created to resolved | Total elapsed time, 24/7; fractions of days are cut off |
| Average Age Chart | Work item age | Average days that open work items have been unresolved | Rising age means old work is not finishing |
| Average Number of Times in Status | Rework | How often work items return to a status | Values above 1 for In Review point to rework loops |
| Two Dimensional Filter Statistics | Work in progress | A table of a filter’s results by two fields, such as status and assignee | Use 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:
- Is work finishing? Created vs Resolved Chart, last 90 days, by week.
- Where does it wait? Average Time in Status for the same filter.
- How long does it take? Resolution Time, last 90 days.
- Is old work stuck? Average Age Chart, and a Filter Results gadget for
resolution = Unresolved AND updated <= -14d. - Where is work in progress now? Two Dimensional Filter Statistics with status by assignee or by type.
- 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:
- Control chart for cycle time and outliers, in company-managed spaces (how to measure Jira time in status).
- Cumulative flow diagram for queues and bottlenecks (how to read a Jira cumulative flow diagram).
- Space insights on the Reports tab, which can show metrics such as average work item cycle time and average time in current status for one space (Atlassian: space insights).
Example: what the dashboard told one team
An example of reading the dashboard together for a team of eight engineers:
| Gadget | Last month | This month |
|---|---|---|
| Resolved work items | 46 | 39 |
| Average time in In Review | 1.6 days | 3.4 days |
| Average age of open work items | 9 days | 14 days |
| Average times in In Review | 1.2 | 1.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.