In our service desk workflow we have several statuses that fall in the category Done. What I am trying to do is create Time to done (Avg.) report, that only tracks the time it took from the creation of the ticket to a specific Done status (Sometimes an issue is moved to "No information" which is a status in the Done category, and after some time it can be changed to Resolved, which is the time I'd like to track)
Is it possible to only track the Avg. time between creation of an issue and a specific Status ?
Hi @dimitar_filipov ,
It is not a built-in functionality in Jira.
Our team at Bloompeak developed Status Time app for this exact need. Additionally, 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).
Here is the online demo link, you can see it in action and try. Hope it helps.
I am afraid this data is not available as a ready to get report on Jira.
The raw data is available in the history of each Jira issue but you would need to get the data from each Jira issue with a REST call and do the calculation yourself. Not an easy development I must say.
I also should say that the best practice while using Jira is to make sure all issues ultimately end up in the same final status and use the Resolution system field to dstinguish between different outcomes for issues.
For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app. 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 as well as entry/exit dates for all statuses.
For your case, you can utilize Time in Status to get the durations of all statuses BEFORE your issues end up in one of Done statuses and combine those durations in any way you like to get the report you need.
A less ideal way (but still possible with Time in Status )would be to use one of the Date Reports of Time in Status to get the dates the issue transitioned to each status and do you own calculations on this data.
By the way, when you get the durations for each status you can also 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 Age, Cycle Time, Lead Time or Total Time Waiting for Customer,etc.
The app calculates its reports using already existing Jira issue histories so you don't have to modify your workflows and when you install the app, you can get reports on your past issues as well.
Using Time in Status you can:
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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