Time in Status

[Devi]

I am trying to add a comment that the issue has been in status for these many days after a transition. I have tried the below two statements in automation and both returns 0.

This issue has been in the status for {{issue.updated.diff(issue.updated).days.abs}} days.
This issue has been in the status for {{now.diff(issue.updated).days.abs}} days.

Any help is appreciated .

[Kalyan Sattaluri]

Hello @Devi 

{{issue.updated}} holds / returns when issue was updated. If your rule trigger is transition of status, it will hold {{now}} value, so what you are seeing is correct/expected.

There is no easy way to do this without third party add-ons because of the complexities of edge cases you have to handle.. (issue moves forward, come back, issue jumps statuses etc)

Please take a look at below article on how to set up a comprehensive way to track this go forward:

https://confluence.atlassian.com/jirakb/how-to-use-automation-to-get-the-time-an-issue-was-in-a-status-1167838219.html

If you dont want to go the extreme route of above article, do a simple rule of capture timestamps of statuses you are interested in and store it in an available (unsed) field / entity property, when an issue transitions and then do a diff.

Both solutions are go forward.

[Amay Purohit_RVS]

Hi @Devi 

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

Time in Status Reports 

The time in status report shows the time spent by your issues in each status during the entire workflow. 

The app has 20+ reports to track your bottleneck Issues & Processes.

More details here 

Disclaimer : I work for the vendor who built this app

[Hannes Obweger - JXL for Jira]

Hi @Devi

I trust that @Kalyan Sattaluri's great answer will help you proceed with the Jira-Automation-based approach.

Just as food for though, in case that you're facing further challenges with Jira Automation: If you're open to solutions from the Atlassian Marketplace, there are a number of apps available that operate in this space.

E.g., my team and I work on an app that I think may be a great fit for what you're trying to achieve: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called history columns that aren’t natively available (including time since status changed, time in [status], and many more), as well as a range of advanced features, including e.g. conditional formatting.

With these, you can build a view like this in just a couple of clicks:

You can also use your history columns across JXL's other advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), or sum-ups. Note that this all just works - so there's no scripting or automation whatsoever required.

Any questions just let me know,

Best,

Hannes

[Mehmet A _Bloompeak_]

Hi @Devi

If you prefer using a marketplace app to get time in status info, 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.

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

App Features:

• 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.

[Iryna Komarnitska_SaaSJet_]

Hi @Devi ,

I can offer you a solution - directly add the amount of time spent in the status to the issue card.

This is possible with the Time in Status for Jira app (developed by my team).

Here's a link to the detailed set guide. The app has a 30-day free trial.

I hope this will be useful to you.

[Gizem Gökçe _OBSS_]

Update on May 9th, 2024: Time in Status by OBSS was recently rebranded as Timepiece. It is still the same capable app with the same dedicated team behind it. The answer below mentions the app as "Time in Status" but you can find the app in the marketplace as "Timepiece (formerly Time in Status)". 

Hello @Devi ,

There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Time in Status which is developed by my team at OBSS, has a report type that will meet your need.  Our app 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. Status Duration report which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc

You can automate a comment on your issues by creating a Jira Automation rule that runs after transitions, requests a Time in Status report via the REST API of Time in Status, and creates a comment based on the result of that report.

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, and in your case this will be the most beneficial solution, so you can get the reports via REST. Also if you need you can export the reports in to various formats easily. 

Visit Time in Status 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.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem