Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any way to get the time spent in a status for an issue

kavita.desai
Contributor
October 12, 2021

I need to know how much time is spent in any particular status of my issuetype bug.

 

5 answers

6 votes
Mayur Jadhav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 12, 2021

Hi @kavita.desai 

Time in Status for Jira Cloud by SaaSJet can improve your reporting and metric.

This plugin automatically brings information that you need:

1. The time in status for each phase in a workflow

2. A number of times an issue has been in each status and went from status to status.

Also, this app generates other reports: average time in status, assignee time to each issue, time in status per date and status entrance date.

Moreover, there are features that allow you to export data and view all reports as charts.

You can get more information and download the add-on at the Atlassian Marketplace.

 

Thanks,

Mayur

Julia Shcherbyna _SaaSJet_
Atlassian Partner
October 20, 2021

Hi @Mayur Jadhav 

Thank you for recommending our program. We are very pleased that it is useful for you.

 

Hi @kavita.desai welcome to the Atlassian Community!

You can view all reports in three views: table, chart, and pivot table.

Try how it works in the demo version without installing the app.

 

Hope you find this add-on helpful.

Regard

1 vote
Zane eazyBI Support
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 15, 2021

Hi @kavita.desai,

If you do not mind using a 3rd party app, you can analyze issue workflow with eazyBI for Jira.

Out of the box, eazyBI offers a set of different metrics to analyze status change history (data from issue history tab), how many times, when, for how long, and who made a status change (see picture below).

eazyBI time in each status.png

You may also check the eazyBI Demo account for more reporting ideas to analyze issue status history or lead and cycle times:
https://eazybi.com/accounts/1000/dashboards/7513-age-lead-and-cycle-time

Best,
Zane / support@eazyBI.com

1 vote
Mehmet A _Bloompeak_
Atlassian Partner
October 13, 2021

Hi @kavita.desai ,

Unfortunately, what you are looking for is not possible with the built-in functionalities of JQL. Because JQL can not make calculations and you need status time to be calculated

For this exact need we developed Status Time Jira app. It provides reports on how much time passed in each status. By grouping statuses you can get resolution time(E.g from new status to done status). You can also export the report as CSV and open it in excel.

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 by any field(eg. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too. 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. Hope it helps.

0 votes
Emre Toptancı _OBSS_
Atlassian Partner
October 13, 2021

Hello @kavita.desai

Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. 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 and each assignee

  tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png

You can calculate averages and sums of those durations grouped by the issue fields you select. For example average resolution time per week, month, issuetype etc.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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.

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.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

0 votes
Rahul_RVS
Atlassian Partner
October 12, 2021

Hi @kavita.desai 

For a readymade solution, you can try out our plugin,

Time in Status Reports 

The add-on provides the time in each status for the entire lifecycle of the issue and you can filter by issue type as well. You can also combine your statuses to define your Resolution time and also extract the transitions history of the issues. The main features of the app are as below

  • More than 8 types of Time in Status Reports. Excel Export available for all status reports.
    • Time in Status
    • Time with Assignee
    • Time in Status with Assignee
    • Time with Assignee per Status
    • Status/Assignee Count
    • Multiple Transition Reports
    • Avg Time reports
  • Status grouping
  • Save your reports
  • CSV Export
  • Multiple chart types

TIS.PNG

Suggest an answer

Log in or Sign up to answer