I need to create a filter to get the number of times a developer go back and forth.

[Julio Martinez Prieto]

I need to create a filter to get the number of times a developer go back and forth from UNDER REVIEW to IN PROGRESS and then to UNDER REVIEW again with his tasks in the sprint backlog. 

[Rahul_RVS]

Hi @Julio Martinez Prieto 

Welcome to the community !!

If you would be interested in a mktplace solution to get this data, you can try out our app.

Time in Status Reports 

The "Per person Status Transitions" report can help achieve this use case as shown below. 

Also this app you can generate time in each workflow status for multiple issues with multiple filter and grouping options. The app has 20+ reports to meet a variety of use cases.

More details here.

Disclaimer : I am part of the app team for this add-on

[Iryna Menzheha_SaaSJet]

Hi @Julio Martinez Prieto 

You're looking to track how many times a developer moves an issue back and forth between "In Progress" - "Under Review" — a common situation during code review iterations.

Native Jira Limitations

Unfortunately, Jira's native JQL cannot count the number of status transitions. It only shows if a transition happened, not how many times.

Example JQL:

status CHANGED FROM "Under Review" TO "In Progress"

This tells you if it ever happened — not how often.

---

✅ Alternative: Time in Status

With the Time in Status app (developed by my team), you can:

• 📊 Use the Transition Count report to see how many times issues transitioned between any two statuses (e.g., from “Under Review” to “In Progress” and back).

• 🎯 Filter by Sprint, Assignee, and Issue Type to isolate only developers’ sprint tasks.

• 📈 Export results to Excel for deeper analysis or display them directly in Jira dashboard gadgets.

Example chart view: how many times each transition occurred

🧪 Bonus Insight

This report is especially useful for:

• Finding bottlenecks in review loops

• Identifying quality or communication gaps

• Coaching opportunities with specific devs or teams

Let me know if you'd like help setting this up — we also offer free demos if you'd like us to walk you through your use case.

Cheers!

[Ayça Erdem_OBSS_]

Hello @Julio Martinez Prieto 

You can get a basic count of how many times tickets transitioned from “ UNDER REVIEW to IN PROGRESS using an app.

If you're open to using a third-party app, I can recommend Timepiece - Time in Status for Jira, developed by our team at OBSS.

For a detailed report showing how many times each ticket has transitioned between “Under Review ” and “In Progress,” our app, Timepiece - Time in Status for Jira,, has several report types that will meet your need. With Timepiece, you can:

Transition Count Report: Track the exact number of transitions between specific statuses for each ticket, which is ideal for monitoring rework and process flow.

JIRA Dashboard Integration: Add this report to your Jira dashboard using the Timepiece Dashboard Gadget to view these metrics in real time.

Timepiece is available for both Jira Cloud and Data Center. Let me know if you’d like help setting up this report or need more information

Hope it helps,

Ayça 

[Mehmet A _Bloompeak_]

Hi @Julio Martinez Prieto

Jira doesn't have a built-in solution for status transition acount. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app.

To get a report of status transition counts, you can have a look at Status Count And Entry Dates report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.

App Features:

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

For further details, you can have a look at Status Time Reports How to Videos.

If you are looking for a completely  free solution, you can try the limited version Status Time Reports Free.

If you have any questions, feel free to schedule a demo with us.

Hope it helps.

[Aaron Williams]

Hi @Julio Martinez Prieto 

Simply, you could look at the ticket history and count the times the status changes from there. 

You would be able to achieve this via custom fields and some kind of incremental count. 

And I'm sure there are an number of Atlassian marketplace apps. 

Each had their own drawback. 

Simply counting is tedious

Custom fields would have overheads and the results would be pretty easy to find by anyone 

Those apps aren't free in most cases. 

I could help create a automation if you are interested in the custom field count option. 

Thanks

Aaron. 

[Julio Martinez Prieto]

Hi @Aaron Williams 

I know that I can look at the ticket history and count the times the status changes, but as you said, it is tedious to count manually the number of times the ticket has been moved to UNDER REVIEW. I will try to create a custom field count option. 

Thank you very much for your recommendation.

Best regards,

Julio