I would like to identify issues that remain too long in the same status so that we can act on this red flag.
The gadget "Time in Status" provides this information but only after the issue has been resolved, which is too late: it looks at past problems rather than help me fix current problems. So it does not work for me.
One option could be to create a custom field "date when status was last changed" which would be automatically updated when a status is transitioned? Or any other suggestion?
Indeed, the best option to have the exact time your issue was transitioned to the current status would be by using a custom field, configuring a post function that would automatically update the field with the current date once it is transitioned.
These would be the exact steps:
- Create a new date/time custom field > add it to your screens
- Navigate to your project > Project settings > Workflow
- Add the post function Update issue custom field to all your workflow statuses, configuring it to update the Custom field with the %%CURRENT_DATETIME%%
Another option would be to use the Time Reports plugin which provides you with the time an issue has spent on each status with the Pivot by Status report.
Let us know if it works for you.
I think the add-on SLA Time and Report if you want to identify issues that remain too long in the same status. You can set SLA timer value and statuses when the countdown should be turned on/off according to your issues workflow, projects and priorities.
I would also recommend using Time in Status for Jira Cloud by SaaSJet could be very useful for you. With this add-on, you can track the number of times an issue has been in a specific status. You can also get the information about the time in status for every stage in your workflow and the number of times a task has gone from one status to another.
In both add-ons, you can use filters to generate reports and later export them as XLSX or CSV file.
Hope, those tools are helpful for you.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events