Easy Tech TutsHow to Calculate Cycle Time in Jira
By Impran M N
Cycle time tells you how long work actually takes once someone starts on it, which is a key signal for spotting bottlenecks. This guide covers how to calculate and view cycle time using Jira's built-in tools.
01Define your start and end statuses
Decide which status marks the beginning of work (like 'In Progress') and which marks completion (like 'Done').
02Open the Control Chart report
On a Kanban board, go to Reports and select the Control Chart, which shows cycle time for completed issues.
03Set the date range and status scope
Adjust the report to cover the date range and specific statuses you defined as your cycle time boundaries.
04Read the average and outliers
Review the chart's average cycle time along with any unusually long-running issues that skew the numbers.
05Use the data to spot bottlenecks
Compare cycle times across issue types or components to find where work consistently slows down.
Frequently asked questions
What's the difference between cycle time and lead time?
Cycle time measures from when work actually starts to completion, while lead time measures from creation to completion, including wait time.
Does Jira calculate cycle time automatically?
The Control Chart report on Kanban boards calculates it automatically once you define the relevant status columns.
Can I calculate cycle time for Scrum projects too?
Yes, though the Control Chart is most commonly associated with Kanban boards; Scrum teams can still apply the same concept manually.
Why does one outlier issue skew my average cycle time?
A single issue stuck in progress for an unusually long time can pull the average up significantly, which is why reviewing outliers matters.
Watch the full walkthrough
The same steps, demonstrated on screen from start to finish.
