Where to find the cumulative flow diagram in Jira
In a company-managed space, go to the space, open the board, select Reports and then Cumulative Flow Diagram. If Reports opens space insights first, select More reports to reach the classic report list (Atlassian: cumulative flow diagram). The diagram is available for Scrum and Kanban boards. Team-managed software spaces have their own version under Reports, which shows data for the whole life of the space; use the date filter to look at one sprint (Atlassian: team-managed CFD).
The diagram follows your board’s setup:
- It includes only work items that match the board’s saved filter.
- Each band is a board column. The left-most column counts as To Do and the right-most as Done.
- Select Refine report to filter it, and use the date range menu or drag across the overview strip to change the period.
How to read the bands
Read the diagram from the top band down. Each pattern points to a different problem:
- A band that widens over time means work enters that column faster than it leaves. Atlassian calls this the usual sign of a bottleneck.
- A band that narrows means the column empties faster than it fills; the team there may have spare capacity (Atlassian: Kanban metrics).
- A flat Done band means nothing is finishing, even if every other band looks busy.
- Evenly rising bands are the goal: work arrives and finishes at about the same rate.
The counts are cumulative. If someone moves a work item back from Done to In Progress, the Done and In Progress areas change but To Do stays the same, so a sudden dip in Done usually means reopened work, not lost work.
- To Do
- In Progress
- In Review
- Done
| Column | W1 | W2 | W3 | W4 | W5 | W6 |
|---|---|---|---|---|---|---|
| To Do | 14 | 13 | 14 | 15 | 13 | 14 |
| In Progress | 6 | 6 | 7 | 6 | 7 | 6 |
| In Review | 3 | 4 | 7 | 11 | 15 | 19 |
| Done | 4 | 11 | 17 | 21 | 24 | 27 |
In this example, Done keeps rising, so the team is shipping. After week 2, the In Review band grows from 4 to 19 work items while In Progress stays flat: developers keep finishing code, and reviews cannot keep up. That is the place for a WIP limit.
How to set WIP limits in Jira
A WIP limit sets the maximum number of work items allowed in a column at once. In Jira they are called column constraints.
Company-managed boards
- Open the board, select More actions (•••) > Board settings, then Layout > Columns.
- Under Column constraints, choose Work item count or Work item count, excluding subtasks. Atlassian recommends excluding subtasks for Scrum teams.
- Enter a minimum, a maximum or both for each column, and save.
When a column goes over its maximum, its header turns red; below its minimum, it turns yellow. The limits never hide cards, and they count cards hidden by quick filters too (Atlassian: configure columns).
Team-managed boards
Open the column’s More actions menu and select Set column limit, or edit the column in the columns and statuses settings and set a maximum number of work items. The column changes color when it holds too many (Atlassian: team-managed columns).
Start from what the diagram shows: Atlassian suggests setting limits only after watching the average number of work items in each status (Atlassian: WIP limits). A limit a little above today’s average for In Review, for example, makes the queue visible without stopping the team.
How to calculate flow efficiency
Flow efficiency is the share of a work item’s cycle time that was active work rather than waiting. Atlassian’s analytics templates define it the same way: active time divided by total cycle time (Atlassian: flow metrics template).
flow efficiency = active time / cycle time × 100%
Example: 2.1 days In Progress + 0.9 days in QA = 3.0 active days
cycle time from In Progress to Done = 6.8 days
flow efficiency = 3.0 / 6.8 = 44%You decide which statuses count as active. Waiting statuses such as Ready for review or Blocked count only toward cycle time. Jira boards do not calculate flow efficiency; the dashboard template above is part of Atlassian Analytics on the Enterprise plan, so most teams compute it from status changes. The Jira time in status guide shows how to get the time per status from the changelog.
What Jira doesn’t show
A cumulative flow diagram counts work items, and flow efficiency treats a status as either active or waiting. Neither shows what happens in between: a work item marked In Progress while the developer spends the afternoon in a support thread, or a review delayed because the reviewer is switching between four tools. Time outside Jira is invisible to both.
hey.space measures that part from activity data: active time per work item, switches between tools and the handoffs between Jira, the helpdesk and chat that repeat every week. Read how hey.space finds automation opportunities, open the sample report or see the Jira integration.