I would like to track how much time any type of issue spends in each of our issue statuses.
For example to answer the question: how much time does an average issue type = 'Bug' with the priority = 'Blocker' spend in the status = 'New' (and 'Registered' and 'In development', et cetera). I also need to keep track of the total time any ticket spent between entering the system as a 'New' ticket, and leaving the system with any of the 'Closed' statuses (such as 'Invalid' or 'Works for me' or 'Fixed' et cetera).
Can anybody point me to the right JQL documentation, or perhaps even share some of the code they use to run such a report in their Jira Cloud environment?
Frankly I'm a bit surprised this report isn't a standard feature of Jira. It's quite important to keep track of this stuff to improve the level of service offered year on year and find out which areas need the most improvement. I can only find addons for which I have to pay an extra subscription fee. But I guess it's possible to make this report myself? I've got no idea how, unfortunately.
At the current moment, it's not possible to get information about time in status using JQL code or using the built-in functionality of Jira Cloud.
You can obtain this data using the add-on like Time in status for Jira Cloud by SaaSJet.
It generates 3 types of reports at the moment:
- Status Count - shows how many times an issue has been in each status
- Transition Count - shows how many times an issue went from status to status
- Time in status - automatically determines for how long your issues had been staying in each status.
Also, you can export the data they need as a report in XLS or CVS format.
Hope it helps
Our team at OBSS created Time in Status app for this exact need. It is available for Jira Cloud, Server and Data Center.
Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group (useful for identifying bottlenecks in your process). You can also see the number of times each status or transition was used (very useful for inspecting reopen counts). Finally you can also create reports on the dates of each issue status transition.
You can produce reports based on the default 24/7 calendar or define your own business calendars with custom workdays and working hours.
Also add system or custom fields as columns to your report and customize the view format of durations.
All data can be exported as XLS, XLSX, CSV.
With new features added to the Time in status for Jira Cloud by SaaSJet, you can easily track how much time any type of issue spends in each of our issue statuses.
Besides Time in Status report, you can measure:
Filter issues by:
Moreover, you can view all of the reports as charts (Pie, Bar and Area Charts).
You can exclude breaks, non-working hours or holidays and create multiple calendars.
Hope, that the new Time in Status for Jira Cloud will help you to create reports you need.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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