Get difference in dates

[Umesh Kulkarni]

Team

Could you please help with this usecase ?

1. I have two dates - when a Issue was approved and when it was marked as done

2. i would like to have a difference between these two days in number of days

3. Once we  this data, i would also like to have average number of days that we take to get the issue moved from Approved to Done.

I am trying to accomplish this using structure but no luck so far.

if( Status = DONE; Resolved - created) - using this in the Jira structure as formula, there is no error nor any value gets populated.

[Mykenna Cepek]

I'm not sure where you're putting your "formula", but I'm not aware of any standard feature in Jira that would handle something like that.

I have two other approaches to suggest:

1) Use a report already built-in to Jira to get what you want. The "Control Chart" in Jira can compute the "average number of days for issues to move from A to B", as well as visualize it for you. I think that chart is one of the most confusing standard reports in Jira, but try it. It might do what you need with no other configuration needed. Under "Refine Report" change the "Columns" settings to exclude status "A" and all the statuses before "A" in your workflow, but select all the statuses after "A" up to and including "B". Then the averages shown at the top should be what you want (mean, median, min and max will be shown for the date range).

2) Jira Automation can do the computation for you, but this approach is a bit complicated to set up. You'll need two fields (reuse existing ones, or more likely create new custom fields). One field (maybe name it "Approved on") will remember the JqlDateTime when the issue got approved. The other field (let's call it "Time to Done") would get set when the issue transitions to "Done", using the built-in diff() function in Jira automation to compute the elapsed time since it was "Approved on". Then you can do reporting on that "Time to Done" field, You'll need two Jira automation rules to set each of these fields accordingly (triggered by the respective Status change). However, you'll want to think through how you want to handle the situations where an issue transitions to either Approved or Done more than once.