metrics about changes in dates

[violeta.marquez]

Hi all,

Is possible to know how many times resolution date was change and generate a report?

[Jack Brickey · Accepted solution]

You could create an automation rule and custom field and increment that field every time an issue moves to a done status category.

[violeta.marquez]

Thank you for the answer, do you know how can I use the custom file for counting? 

[Jack Brickey]

First to be clear I assume what you're wanting to count here is the number of times an issue is in affect re-opened since resolution date basically is set when issue is marked done.

you can use Automation to increment the field.

trigger - issue transitioned

Condition - status = done 

Action - use math expressions to add +1 to current value - smart-values-math-expressions 

[Joshua Sneed Contegix · Accepted solution]

Hi Violeta,
That is probably possible. Changes to fields are collected in the issue history and can likely be pulled/processed with an appropriate plugin within Jira or solution external to Jira, but I have not worked out the specifics around how. Cheers!

[violeta.marquez]

ohh thank you for the answer, is possible to generate a query to obtein history?

[Joshua Sneed Contegix]

Hi Violetta,

Probably, almost anything is possible if you dig into it far enough. Check out other posts on Community or look through jira.atlassian.com.

• https://community.atlassian.com/t5/Jira-questions/How-to-get-issue-history-with-JIRA-API/qaq-p/1290968
• https://community.atlassian.com/t5/Jira-articles/Extracting-complete-issue-history-via-API/ba-p/1659204
• https://jira.atlassian.com/browse/JRASERVER-27692

Cheers!

[Bill Sheboy · Accepted solution]

Hi @violeta.marquez 

How often do you need this information and for how many issues? 

Just a few?  Please look at the issues' history log.

A few more...and are willing to experiment with the REST API and JSON, you could call the function to get the change log history and count things in your final status.  You may use this for previously completed issues rather than only doing this going forward.  Of note:

• you would need to call this issue by issue,
• if you have more than 100 changes per issue, you would need to page through the results with multiple calls

And, you could combine this with Jack's idea to retroactively set the custom field counter for issues which were resolved prior to the automation rule's creation.

Best regards,
Bill

[Yuliia_Borivets__SaaSJet_]

Hi @violeta.marquez 

There are two options you can check out.

1. Time in Status for Jira Cloud add-on: With the Status Count report you'll get the number of times some issue moves to resolved or another status.

2. Issue History: With this app, you'll get a history diary for every activity and find out what changes were made to the issues, by which user, and when.

These apps are developed by my team, so feel free to write if you've got any questions.

[Mehmet A _Bloompeak_]

Hi @violeta.marquez ,

The data you need is available in issue history and you can get it using Jira Rest API. It provides the exact resolution date changes for each issue. It returns json, then you need to calculate it by coding which parses issue history rest api json for each issue.

Or you can try marketplace apps. We developed Status Time Jira app for this exact need. By default it displays time in status but it can also report resolution date changes. You need to select "Report for resolution" and "Report type: List" along with "show count" a and "show entry dates" toggles on. Here is the online demo link, you can see it in action and try.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.