Average Time in Status

Knowing that a ticket took 10 days to complete tells you very little. Knowing that 8 of those days were spent waiting in “In Review” tells you exactly where to intervene. This visual shows you the average time issues spend in each workflow status per project — revealing where work gets stuck, not just how long it takes overall.

Different projects will have different bottleneck profiles. One may be slow in review, another may have a backlog that issues sit in for days before anyone picks them up. Seeing both side by side helps you direct process improvements to the right stage.

What you can conclude

• A status with a disproportionately high average time is the primary process bottleneck — focus improvement efforts there, not on execution speed.
• If the same stage (e.g. “In Review”) is slow across all projects, the problem is structural — a shared resource or process constraint.
• A project where “To Do” dominates all other stages has a backlog problem, not a delivery problem — grooming is the priority.

How this chart works

Grouped bar chart showing average hours issues spend in each workflow status, grouped by project. Toggle to table view exposes median and P90 times per status. Use the project filter to focus on a single team.