Read Jira Control Charts
Use the control chart to inspect cycle-time distribution for a consistent process and scope. An average alone can hide outliers and changes in what the chart measures.
Step-by-step guide
Check access and scope
Use a supported software report and confirm board status mapping. Decide which workflow interval represents cycle time for the question you are investigating.
Open the control chart
Open the board report and choose the control chart.
Choose comparable scope
Set a period and comparable issue scope.
- Worked example: A long review interval for invitation changes may reflect a missing security reviewer, not slow implementation. Inspect individual histories before attributing the pattern to a person or team.
Inspect measured statuses
Inspect the selected columns or statuses used for the interval.
Read outlier histories
Open outliers and compare issue histories.
Record a process hypothesis
Record a process hypothesis and review another comparable period.
Verify the result
The chart interpretation names its scope, interval and specific examples supporting the proposed bottleneck.
Common mistakes
Avoid the main failure mode
Comparing different issue populations or workflow intervals produces misleading trend claims. Keep scope and measurement definitions stable.
Check the handoff edge case
Changing measured columns between periods changes the definition of cycle time. Record the interval before comparing trends.
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.