nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Status change counter

Enrique BESUMAN BARCENAS_kir68n

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

Accepted answers

Marc -Devoteam-

Hi @Enrique BESUMAN BARCENAS

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.

Nikola Perisic

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

All comments

Marc -Devoteam-

Hi @Enrique BESUMAN BARCENAS

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.

Nikola Perisic

Hello @Enrique BESUMAN BARCENAS

There was a discussion to this topic here: https://community.atlassian.com/forums/Atlassian-Home-questions/Project-status-and-date-relationship/qaq-p/2640238

Enrique BESUMAN BARCENAS_kir68n

Thanks Marc, that's a great idea!!! I'll check if I have the rights in Jira to do that.

Enrique BESUMAN BARCENAS_kir68n

Thanks Nikola, I'll try the automation/custom field idea, I just need to ask my admin for the permission to create automation.

Birkan Yildiz _OBSS_

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.

Khrystyna_Dzhus_SaaSJet_

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.

Untitled design (34).png

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.

transition report.png

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

Danylo Iliukha _Appfire_

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

Danylo Iliukha _Appfire_

@Enrique BESUMAN BARCENAS

If setting up automation rules is awkward or you want the count across many issues at once without maintaining a custom field, here is another option.

If you are open to solutions from the Atlassian Marketplace, JXL for Jira includes history columns derived from each issue's changelog. Add Number of statuses, configure it for Open, and JXL shows how many times each issue entered that status. Load your filter or JQL in a sheet, sort by that column, and the highest counts surface the rework-heavy tickets.

number-of-status-changes

No automation rules or extra custom fields required. The value is visible in the sheet and you can export it if needed.

I work on the team that builds JXL.

Thanks,
Danylo

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud