Read Jira Cumulative Flow Diagrams
Use cumulative flow to inspect how work accumulates across statuses over time. A widening band suggests a queue worth investigating; it does not identify the cause by itself.
Step-by-step guide
Check access and scope
Confirm the report supported by your board and inspect which statuses are represented. Avoid comparing periods with unexplained workflow changes.
Open cumulative flow
Open the cumulative flow report for the relevant board.
Set a stable period
Choose a useful date window and stable scope.
- Worked example: If Review grows while Done barely changes, investigate whether reviewers lack capacity or evidence is repeatedly missing. Starting more implementation may increase the queue rather than improve throughput.
Find widening active queues
Identify bands that widen persistently rather than briefly.
Inspect issue movement
Inspect representative issues entering and leaving the queue.
Agree a process adjustment
Agree on one process adjustment and review the next period.
Verify the result
The review identifies a specific queue, supporting issue examples and an action whose effect can be checked later.
Common mistakes
Check the handoff edge case
A workflow change can alter the chart population or status bands. Note configuration changes before comparing periods.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.