Report time in status

[Aswathi D]

---

Without any add-ons is it possible to know how much time each each issue spend on each status

[Bill Sheboy]

Hi @Aswathi D 

Yes, using the built-in control chart report: https://confluence.atlassian.com/jirasoftwareserver/control-chart-938845628.html

Note there are some limitations with this report, such as when there are a cluster of issues for a particular time measure and when the y-axis rescales, etc.  

Kind regards,
Bill

[Aswathi D]

Hi @Bill Sheboy ,

thank you for pointing out the control chart as a possibility. I tried it and in principle, it serves our purpose. However, I cannot filter by status as I would like and I cannot see how long the CRs have remained in which status.

Specifically, we are looking for an output that can deliver the following:

• average lifecycle time and CR-specific lifecycle time
• average duration of CRs in the individual stages and CR-specific duration in the individual stages
• and filtered according to CRs that have already been completed (done, rejected) and CRs that are still being processed (all other stages)

How can I achieve this with the control chart? Or in another way?

[Bill Sheboy]

You may find some of the average information at the top of the chart, and the specifics for items by selecting them on the chart.  One limitation of this chart is when multiple items have the same total time, they are grouped in a larger "cluster", which hides the individual details.

Regarding filtering by status and other things, that can be done using the built-in chart options and / or the use of quick filters for the board.

If you have a need to perform further analysis with the measures, a marketplace addon  may be better as it may permit exporting results.  You could also build your own application with pull each issue's history for analysis elsewhere.

[Amay Purohit_RVS]

Hi @Aswathi D 

If you are open to try out a mktplace app, you can take a look at 

Time in Status Reports 

One of the many reports which the app provides is Time in Status in hours/days to determine , how much time the issue spent in each status in the complete lifecycle of the issue. The app has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app

[Valeriia_Havrylenko_SaaSJet]

Hi @Aswathi D 👋

If you are switching to cloud or data center - Time in Status for Jira one of the best tool for monitoring how much time each each issue spend on each status. Also we have 7 types of status time reports such as Time in Status, Assignee Time, Average Time. All the reports you can display as Pie, Bar or Area Charts.



Also you can get cycle and lead time to uncover bottlenecks and delays

And last, but not least - we have Sprint Performance Report Sprint Performance Report where we have all the metrics for easy reporting.

Add-on has a 30-day free trial version and free up to 10 users. 
Hope it helps 😌

[Mehmet A _Bloompeak_]

Hi @Aswathi D

If you consider using a marketplace app one day, 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. For your case, you can have a look at Time in Status for Each Issue report. You can filter by Issue Type, Status, Assignee, Created fields or by typing your own JQL(using "Switch to JQL" button).

For further details, you can have a look at Status Time Reports How to Videos.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. 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.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

[Gizem Gökçe _OBSS_]

Hello @Aswathi D ,

I understand that you are not looking for a paid solution right now. However, if you ever need it I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for both Jira  Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

You can combine the time for multiple statuses to get metrics 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. 

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 for Jira Cloud.

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.

    

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features. 

Hope it helps,

Gizem