How to get the date of the last status transition?

[mateus_oliveira]

We weren't aware that setting a issue as "Done" was not the same as "Resolving the issue". Now, we're trying to get some reports and some of them are dependent on the date the issue was finished.

"Last update date" wouldn't be enough, as sometimes we update issues that were already finished (for N different reasons) with new info or records. It really would have to be "Last Status Transition".

I assume this would have to be accessed using Smart Values, so it could be used in Automations or CSV Imports.

{{issue.statuscategorychangedate.toDate.jiradate}}

For some reason, the code above doesn't work. I tried multiple syntaxes, all Camel-cases, all lowercases, with and without toDate and jiradate, etc, but anything I tried was capturing no value for an issue that did transition through multiple status...

Is this possible? Am I missing something?
Any tips are appreciated, thanks!

edit: I don't have the option of using any third-party app nor the marketplace etc because I use a company managed instance.

[Gizem Gökçe _OBSS_]

Hello @mateus_oliveira ,

The required data, which is the first transition date to status Done, is available in each issue's history. However, extracting it manually requires building a custom solution. A simpler approach is to use a Marketplace app that provides ready-to-use reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal with Jira issue histories. The app is Timepiece -Time in Status for Jira , the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center. 

With date-based reports, you can track transition dates for each status. In the screenshot below, you’ll see the first transition dates of issues into each status. The highlighted column in your case will provide exactly the data you need.

Reports are available via the reporting page, dashboard gadgets, and issue view screen tabs, with both data tables and charts. Timepiece also offers a REST API for seamless integration and supports CSV/XLS exports.

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features. 

Hope it helps,

Gizem

[Petru Simion _Simitech Ltd__]

Hi @mateus_oliveira ,

Non app solutions:

• If you have alreay issues that you need to find out the last time the status was changed, you can visuall inspect the history of each issue.
• I you want to automate this you can create a scripted field, assuming you have Script Runner. The script field will search the last date the status was changed in the issue history and provide the value. Later you can use JQL to retrieve your issues matching a certain from to criteria for the last history change date. This will not allow you easy rporting though.

If you are open to using apps you can use Issue History Dashboard for Jira , an app released by our company.

You will filter Field Updated = 'status' and sort the result by Date of Change.

This will give you the last time the issue was transitioned for each issue.

You can also export to csv and use Excel for more data drilling and sorting.

Regards, 

Petru

[Hannes Obweger - JXL for Jira]

Hi @mateus_oliveira

I'm not an Automation expert, so perhaps someone else can lean in for specific advice.

Just as food for thought: If you're open to solutions from the Atlassian Marketplace, there's a number of apps available that will help you surface the last status transition date of your issues, without any scripting or automation needed.

E.g., I can warmly recommend the app that my team and I are working on: 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 long list of so-called history columns that aren't natively available, including the date/time of transition to [status], time in [status], time between [status] and [status], and many, many more.

This is how it looks in action:

As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. Of course, you can also export your data to Excel or CSV in just two clicks.

Any questions just let me know,

Best,

Hannes