Jira Control Chart vs Cumulative Flow Diagram — which shows your bottleneck?

Jira’s Control Chart and Cumulative Flow Diagram (CFD) both plot time along the bottom and get mistaken for each other. The Control Chart plots cycle time per completed issue as a scatter chart — a duration report, useful for “are we getting faster?” The CFD plots how many issues sit in each status over time as stacked bands — a work-in-progress report; a widening band hints that issues are piling up in that status. Neither gives you the one number that actually names a bottleneck: how long issues spend in each status. Here’s what each shows, what neither tells you, and how to get that number.

What each report shows

• Control Chart — plots cycle time per issue over time: for each completed issue, how long it took to get through. It’s a duration report. Good for “are we getting faster?”, weak on “where does the time go?” Available on company-managed boards only.
• Cumulative Flow Diagram — plots how many issues are in each status over time, as stacked coloured bands. It’s a work-in-progress report. A band that widens means issues are accumulating in that status. Available on both company-managed and team-managed projects.

So they’re complementary: one is about how long finished work took, the other about where work is piling up right now — and the CFD is the one you’ll still have if your team runs a team-managed project.

What neither one tells you

Both stop just short of the useful answer:

• The Control Chart gives a single blended cycle-time number per issue. It doesn’t split that time across the statuses the issue passed through, so it can’t say which stage was slow.
• The CFD shows a widening band — a hint that a status is congested — but it’s a visual read, not a number. It doesn’t tell you how long an individual issue actually sits in that status, and it’s tied to one board.

In other words: the CFD suggests where to look, the Control Chart tells you the total, and neither gives you the concrete per-stage duration you’d act on.

Turning the hint into a number

The direct measure of a bottleneck is time in status — how long issues actually spend in each stage. That turns the CFD’s widening band into “issues sit in Code Review for 3.2 days on average,” which is something you can take to a retro.

Linger reports time in status across issues, so the stage the CFD only hints at becomes a number you can name — and the blended figure from the Control Chart breaks down into where the time really went.

Why the per-status view finishes the job:

• Names the stage — not “something’s congested” but “Code Review is the slow step.”
• A number, not a colour band — hours or days per status, comparable across issues.
• Not board-locked — measure the statuses that matter, however your workflow is set up.

This is the same gap the Control Chart leaves on its own — see Jira’s Control Chart vs time in status — and it’s what lets you compute the two clocks in cycle time vs lead time in Jira from real durations.

Which should you use?

• Tracking whether delivery is speeding up over time? The Control Chart.
• Watching where work-in-progress is building up? The Cumulative Flow Diagram.
• Trying to name and fix the bottleneck? Measure time in status — a tool like Linger turns both reports’ hints into the per-stage number you actually act on.