Status change counter

Hi @Enrique BESUMAN BARCENAS 

Jira does not expose a built-in column or JQL function for "times in status," so you usually build the metric yourself or use an app.

Quick manual check
Open a work item, go to Activity > All, and filter or scroll through status changes. That helps for one issue, but it does not scale if you want to rank many tickets.

Automation + number field (native)
This is the most common native setup:

1. Create a Number custom field, e.g. "Times in Open."
2. Create an automation rule with trigger Issue transitioned (scope it to transitions into Open, or whatever status you care about).
3. Add action Edit issue fields and set the counter to `{{issue.Times in Open}} + 1` (use your field's smart value name).

You may need separate rules if issues can return to Open from multiple statuses. Test on a few issues first, since the first transition into Open on creation may or may not count depending on how your workflow is set up.

JQL limitation
You cannot sort or filter by that counter in JQL until the custom field is populated, but once the automation runs, you can use it in filters and dashboards.

Hope this helps,
Danylo

Hi @Enrique BESUMAN BARCENAS 

Great question — this "bounce back to Open" pattern is one of the clearest signals of hidden rework, and native Jira won't count status re-entries for you without custom automation or manually digging through each issue's history.

The quickest way to get this exact metric is a Marketplace app. With Time in Status by SaaSJet, you can pull it in a couple of clicks:

You can see how many times issues have entered a status Open or any other one by using the Status Count report. You can sort by column and see the most problematic issues at the top. 

Another type of report Transition Count allows you to look at the specific transition into Open (e.g. In Review → Open). That isolates the actual "kicked back to Dev" loop and filters out the initial entry.

Full disclosure: I'm part of the SaaSJet team behind Time in Status. Hope this helps you track down those rework loops!

Hey @Enrique BESUMAN BARCENAS

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.