Can we product a report to see how long an issue has taken to move status

[Mihir Ruparelia]

Hello, 

I have had a question from a user, they want to know how long an issue was in status To Do for before it was moved to In Design. 

I have been doing lots of reading and I can't find any answers apart from the Time in status app for JSM. 

Could anyone let me know if they have been able to do this via a filter or reporting within Jira. 

[Sid Pathirana]

You can do with using the built-in features in workflow and/or automation in your JSM Standard cloud subscription plan by:

1. recording the timestamp of the transition into each of the <To Do> and <In Design> statuses in your workflow
2. calculating the time difference between the above two timestamps.

I've done a similar thing to calculate the lead time & cycle times for tickets using the built-in features in Jira as we don't have any third-party apps yet and the built-in Control Chart report is too awkward for this purpose. Once you've got this data recorded at a ticket level, then it can be easily filtered, reported or exported via the built-in functions.

---

1) Create some custom fields to hold the data, eg:

• "Timestamp: To Do", field type: Date Time Picker
• "Timestamp: In Design", field type: Date Time Picker
• "Duration (To Do - In Design)", field type: Number field

2) Add the custom fields to the screens on whichever ticket type(s) you want to record this against. 

If your workflow transitions are defined so that once you move into <To Do> or <In Design> then you can't return to those states, then you can use a workflow postfunction to record the timestamp for when the transition occurred.

3a) Add workflow postfunction to <To Do> and <In Design> transitions: Update Issue Custom Field

If your workflow transitions are defined so that it is possible to return to the same states after you have initially moved into <To Do> or <In Design> then you may want to ensure that you only record the timestamp of the first occurrence rather than the most recent occurrence (the workflow postfunction method will reset to the most recent occurrence).

3b) Use Jira Automation to record the timestamp

• I would recommend restricting the automation to your particular project(s) and the specific ticket types and statuses to reduce the scope of the rule as much as possible to avoid unnecessary charges in the new automation billing policy.

4) Once each ticket is resolved/completed, then use another automation rule to calculate the duration between the two timestamps and store it in the custom field created earlier.

• Field: Duration (To Do - In Design)
• Formula: {{issue.Timestamp: To Do.diff(issue.Timestamp: In Design).minutes}}