A cycle time is the time that it takes to a unit to get through a workflow, including each step of the way. For example, if I have a User Story that will go from the backlog to a developer (In Dev), then to Ready for QA, then get pulled by QA (In QA), and then go to Acceptance, I can measure how long the unit is in each of those fields. So the cycle time is the time that it is in those fields and the total time from start to finish. Jira already captures this data, if you go to the reports screen and select "Control Chart" you can find cycle time info for a specific timeframe - hover over one of the circles on the chart and it will give you the detail.
This is a pretty old post but since you guys are following, let me give you some detail:
The data that can be used to produce reports like Issue Age, Cycle Time, Lead Time are Issue History Data but Jira does not give these data in a UI report.
For Jira Cloud users, you can get this raw data through REST API. For Jira Server and Data Center users, you can get this raw data from the database directly (changelog & changelogitem tables). In either case, this is unprocessed raw data, only issue field changes and dates of those changes, pretty much the same stuff you see in the History tab of each issue.
You would need to do some custom development to turn this into a useful report.
Having said that, I want to note that our team at OBSS built Time in Status app for this exact need. The app processes the issue history data and produces ready to use report. It is available on Atlassian Marketplace for Jira Server, Cloud and Data Center.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype). You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time.
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
You can export your data as XLS, XLSX or CSV and also get processed report data via REST API.
Just to make sure we are thinking of this the same way: The control chart does capture cycle times and you can leverage quick filters to dig into the data a little bit better. The challenge is when you want to dig I'm even further to better identify waste and bottle necks and other trends, especially across many teams. Being able to export the data would be ideal for that but it's not possible.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events