Hello,
I am wondering if there's a way to show on a dashboard a report of how long each ticket within a project or queue has been in each status of the workflow.
I've used the "average time in status" tile on many dashboards but my team is asking to break that down into detail by individual ticket and how long it spent in each status, does anyone have the best way to accomplish this?
Thanks!
Hello @Kyra Mayock
In addition to the answers below, I would like to recommend you the add-on called Time in Status for Jira Cloud. which generates 7 types of status reports, including a Time in Status one. Your team can track how long the issue has been spent in each status on the dashboard, charts view, or even directly on the issue card layout (will be released in a few days).
It is developed by my SaaSJet team. Please, let me know in case you have any questions.
Hope you find it helpful.
Hello @Kyra Mayock ,
If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee.
The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.
For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.
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. It supports both Company Managed and Team Managed projects.
Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.
And the app has a REST API so you can get the reports from Jira UI or via REST.
Using Time in Status you can:
https://marketplace.atlassian.com/apps/1211756/
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kyra Mayock
As an alternative, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.
Here is the online demo link, you can see it in action and try without installing the app.
If you are looking for a free solution, you can try the limited version Status Time Free.
Note: If you are interested in cycle and lead time, you can have a look at the article below.
Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kyra Mayock
If you are fine with a mktplace app, you can try out our add-on to get this data.
You can also groups your statuses to get the total resolution/cycle time.
The main features are as below
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kyra Mayock
Create a saved filter to match the issues you want to know about and then have a look at the Cumulative Flow Diagram to see if that helps part of standard dashboard reporting.
Hope that helps.
Phill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Phil,
I don't see that under reports for service projects, is it something you have to define and build yourself, or is that for software projects that run in sprints etc.?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.