How can I know the number of times an issue has passed through a specific status?
When we review an issue if the find errors we put it back in to Open Status so the Dev team will pick it up and fix it.
In this scenario I'd like to know how many times an issue has been in the Open Status. - it will point me to the "problematic" issue
You can create a field for this, custom number field and create an automation that based on a specific status change the number of the field will update +1
There might also be apps on the marketplace to provide such infrmation.
Thanks Marc, that's a great idea!!! I'll check if I have the rights in Jira to do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Enrique BESUMAN BARCENAS
Either you this by clicking on the All withing the Activity section of the work item. You also make sure that you are a watcher for that work item. It doesn't tell you the the exact number, it gives you the picture of problematic work items.
Another option you have is creating another custom field which will be tied to an automation rule that for every transition (and this transition would need to be defined differently as a part of multiple automation rules) would add an increment to the custom field by 1.
There was a discussion to this topic here: https://community.atlassian.com/forums/Atlassian-Home-questions/Project-status-and-date-relationship/qaq-p/2640238
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nikola, I'll try the automation/custom field idea, I just need to ask my admin for the permission to create automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tracking how many times an issue bounces back to a specific status (like "Open") is crucial for identifying rework, but native Jira doesn't offer an out-of-the-box report to count these status re-entries without relying on complex automation rules.
If you are open to using a Marketplace app, you can easily get this exact metric using Timepiece - Time in Status for Jira.
Here is how you can set it up to find those problematic issues:
Use the Status Count Report: This specific report lists your issues in rows and statuses as columns. It automatically calculates and displays the exact number of times each issue entered the "Open" status based on its history.
Sort and Identify: You can easily sort the report by the "Open" column to instantly bring the issues with the highest reopen counts (the most problematic ones) to the top of your list.
You can read my Atlassian Community article about this topic to learn more.
Timepiece Assistant: You don't even need to configure the report manually. With the built-in AI Timepiece Assistant, you can simply ask in plain English (e.g., "Show me how many times issues entered the Open status"), and it will instantly generate a ready-to-use report link for you.
You can find Timepiece - Time in Status for Jira on the Atlassian Marketplace. BTW, after installation, you can instantly create reports on past issues.
Full disclosure, I'm on the team that makes Timepiece. Hope this helps you find your workflow bottlenecks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.