We are on JIRA v7.10.0 and it seems that the Control Chart is not providing the information we need to calculate lead & cycle time because it uses a rolling average based on a number of issues, not the actual average time for all items in that sprint.
Why am I seeing a rolling average drastically changes across a 10 day sprint? I have changes of 5+ days in the rolling average overnight. I get that you might want the default setting to be based on a sampling of issues, but if I change to criteria and ask for a customer date range...why can I not get an average of ALL issues? Please save your time if you answer is 'buy my add-on...', Jira should be able to provide this functionality out of the box.
I like to look at the individual issues to measure those values. Lead time is easy to find by running a query for the issues you want to view and make sure that 'created' and 'resolved' dates are listed in the columns that you want to export.
Cycle time is a bit trickier. If you are able to create a custom filed that captures the time an issue goes into 'working' status, then you can include that value in your export and then you can view cycle time per issue.
Lead Time = created -> done
Cycle Time = working -> done
Hello @Rafael Macedo ,
For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available 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. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time.
You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the total InProgress time per Epic, or average Resolution Time per issuetype).
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.
The app has Custom calendar support that your are looking for. This feature enables you to get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)
Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.
Using Time in Status you can:
Hello @Rafael Macedo ,
Time in Status is not part of standard Jira offering. It is available as a separate app on Atlassian Marketplace. You can see and install the app from the Marketplace link below:
Once it is installed on your Jira, you can access the app using the Time in Status link in the main Jira menu.
Hi @Rafael Macedo ,
For an automated solution, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count.
Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).
When working in customer support, it’s crucial to calculate, analyze and monitor specific numbers, called KPIs (Key Performance Indicators). They go hand-in-hand with customer satisfaction, problem d...
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