Is there a way to get the date and time for when issues transition from one status to the next?

[Teri Simonds]

We have an SLA with our client where we are required to track Mean Time to Repair in business days (hours and minutes).  Jira provides a Created Date/Time and a Last Modified Date/Time but what would best is to get a date/time for each step of the issue workflow (or development life cycle), without having to look at the history for each issue.

We also are required to provide a count of issues that have been reopened during the reporting month (the "recidivism" rate).  I'm not sure how we can get that information, especially if the issue is reopened and resolved on the same day.

Are there queries that can provide this level of granularity?

Thanks!

[Rahul_RVS_Support]

Hi @Teri Simonds 

For an alternate solution, to get this data you can try out our app.

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 lead/cycle/resolution time and also extract the transitions history of the issues. The main features of the app are as below

Also there is a report for the dates when issue transitioned from one status to another.

• Multiple 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 in status reports
  • Status Change Dates Report
  • Time in Status Per Time Grain
  • Time with Assignee Per Time Grain
• Status grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

[Bloompeak Support]

Hi @Teri Simonds

It is not an out-of-the-box feature in Jira. However, there is a good solution for your request - Status Time Reports app developed by our team. It can display status entry dates and count of issue statuses(in your case count of issues that have been reopened) as can be seen below.

It also provides reports on how much time passed in each status. It has grouping feature so that by grouping statuses(In Progress → In Review → Done) you can get total time. 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(e.g. 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.

[Emre Toptancı _OBSS_]

Hello @Teri Simonds ,

If you are OK with using a marketplace app for that, our team at OBSS built Time in Status app for these exact needs. 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 on each assignee. 

       

Time in Status 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 perfect to get measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

The app has Status Count and Transition Count reports which show you the number of times each status and each transition was used respectively. These are perfect for reporting on reopens.

For all numeric report types, you can calculate averages and sums of values grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

The app has 4 different date reports that show the first/last transition date from/to a status.

The app has custom calendar support. Using this feature, you can define multiple custom calendars, each with its own working days, working hours, holidays, and time zone. When a report is prepared using a custom calendar, the non-working hours will be excluded from the report. (This is a nightmare when you try to calculate this from scratch using transition dates.)

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.

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:

• 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

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Rodney Nissen - ReleaseTEAM]

Well Teri, I have some bad news.

Under the default configuration, there isn't a way to query this.  HOWEVER.

With the right Apps, you can configure post functions at each transition that captures what you need into custom fields.  Either JSU or JMWE would be able to set the appropriate fields with the current timestamp.  Then it's a matter of querying all the fields that have this populated and extrapolating from there. 

For Reopening the Issues, this is easy enough to do once the same way, but if a issue is reopened multiple times, that approach would only show for the latest reopen.

Another option would be using those Apps to set a comment, though that is harder to query for.