Question about time duration of workflow status change

[Jason Liu]

Hi, our user wants to get the time duration between two specific workflow statuses. We know that we can only get it through calling issue API. But is there any other auto way to do this? Just like automatically put the time duration value to a specific field value through some extra function? 

[Lucy Warner_SaaSJet]

Hello @Jason Liu 

You can try both the automation and the add-on from the Atlassian Marketplace.

But a third-party add-on gives you more opportunities and features to use. That's why I guess trying Time between Statuses (sever version) to calculate how long it takes an issue to move between statuses.

Also, you can export a report to CSV or XLSX files if necessary.

This add-on is developed by my SaaSJet team and it's free for teams up to 10 users. Please, let me know if you have any questions.

I hope you find it helpful.

[Mehmet A _Bloompeak_]

Hi @Jason Liu

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.

• 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, 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 free solution, you can try the limited version Status Time Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello  @Jason Liu

You can try building a solution with Automation but it will have to be replicated (and maintained) for each timespan you want to report. And it will not work for your past issues. On the other hand, the data needed to calculate this report is available in each issue's history.

I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. 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. 

       

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. This report type 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.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user the exclude the times for "pause" statuses.

  

These reports show a list of issues by default so you can see the metric values for each issue separately. Also, for all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total cycle 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.

Time in Status 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:

• 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

[Alex Koxaras -Relational-]

Hi @Jason Liu 

You can calculated the difference between two different date time fields and when transitioned to the next status, then place this value to a new text field. There are also apps which can calculate the time in status and between statuses.

[Jason Liu]

Hi Alex, I saw there's Time In Source Status in issue activity-transitions. Can I get this value exported? Or if I have a custom date time field, how can I copy this value to the field?

[Alex Koxaras -Relational-]

@Jason Liu I don't use the specific app. If I were you I would try with API to get the issue's fields and see if that custom field is included there. If it's there, then problem solved!

Try using the https://yourbaseurl/rest/api/2/issue/ISSUEKEY to get the info and search for either seconds or that specific value in pretty print, of microseconds or for a timestamp.

[Jason Liu]

Hi Alex, we have scriptrunner app in our system. Do you know if it can make automation happen? Just put the time in source status value to a specific time field value by script.

[Alex Koxaras -Relational-]

@Jason Liu if you have scriptrunner, I would suggest to try and create a scripted field and then calculate the difference you want and place it on that new field.

[Jason Liu]

Hi Alex, you mean use script runner to calculate the difference and also use script runner to place the value on a field? Do you know how to do the calculation?