Report on each how many times a ticket sent back from testing to dev

[Lubna Malik]

Hi All!

Management is wanting to see how many times an issue goes BACK in our process. for example:

We have 5 states:

> Dev > Testing > Preprod -> Prod

If the ticket moves all the way to Preprod, then it goes back to Development (er, because of a bug), is there a way for JIRA to tally this and display a report in a Dashboard?

For example,

• Issue DS03 went BACK from Testing to Dev 3 times during the life-cycle
• Issue DS03 went BACK from Preprod to  dev 3 time during the life-cycle

Metrics like that....is it possible? or can the data with extracted out of Jira in csv format

[Dick]

Hi @Lubna Malik 

Yes this is possible!

You would need two custom field to store the number of times a ticket is sent back (one for tickets from PreProd, one counter for tickets from Testing).  An automation on the status change of a ticket can be set to fire if the smart value {{issue.status.fromString}} would be Prod /Testing and the {{issue.status.toString}} would be Dev. 

Depending on the preprod or testing, the number in the designated custom field would get increased and stored on the issue. 

That way, you can report on any ticket the amount of times it was sent back to development after being in preproduction and how many times it was sent back after being in testing.

Happy automating!

Dick

[Hannes Obweger - JXL for Jira]

Hi @Lubna Malik

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren’t natively available, including number of transitions to [status], number of transitions between [status] and [status], and many, many more.

This is how it looks in action:

As you can see above, you can easily sort and filter by your history columns. You can also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. With these, you'll be able to build a useful report in just a couple of clicks.

Any questions just let me know,

Best,

Hannes

[Vitalii_Bobak_SaaSJet]

Hello @Lubna Malik 

If you are open to add-ons , try out Time in Status.

For your exactly need we have Status Count report or Transition Count report

The Status Count report shows how many times an issue has been in each status.

Also you can view the report by Chart in add-on or configure it as a Dashboard Gadget (both Grid and Chart available):

The Transition Count report shows how many times an issue has moved between all statuses in the workflow.

Chart view of report:

You can also book a live session or contact us at Support - we'll help you with Time in Status. 

Add-on developed by my team.

I hope you find this helpful 🚀

[Rahul_RVS]

Hi @Lubna Malik 

There are few ways to achieve this requirement. You can use Jira Automation to populate a custom field on status change. or you can also use Jira Rest API's to pull this data from issue change history.

Another option could be to use a mktplace app. If you would be interested in the same, you can try out our app 

Time in Status Reports 

The below report will suffice the requirement. This transition report shows how many times the issues went from which status to another. Also with this app you generate time in status for multiple issues with multiple filter and grouping options. The app can easily be added as a dashboard gadget.

More details here.

Disclaimer : I work for the vendor who built this app

[Manoj Gangwar]

Hi @Lubna Malik,

You can check the issue history to see if the issue transitioned from one status to another, but you can not export and create a report.

As a workaround:

• You can set up an automation rule that triggers whenever an issue moves from a later status (e.g., Testing or Preprod) back to Development.
• Each time this happens, the rule could increment a custom field (e.g., “Back to Development Count”) on the issue. This custom field would store the number of times an issue has reverted, and you could display it in a dashboard gadget or include it in filters and reports.

[Mehmet A _Bloompeak_]

Hi @Lubna Malik  ,

There are below solutions.

1. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides the status changes for each issue. It returns json, then you need to calculate status change count by coding which parses issue history rest api json for each issue.
2. You can try marketplace apps. We developed Status Time Reports app for this exact need. Here is the online demo link, you can see it in action and try. If you are looking for a free solution, you can try the limited version Status Time Free.

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

[Gizem Gökçe _OBSS_]

Hello @Lubna Malik ,
You can get a basic count of how many times tickets transitioned from “QA” to “In Progress” using a JQL query in Jira. Here’s a quick way to do this:

JQL Query: You can use the following JQL query to see all tickets that have transitioned from “Dev” to “Testing” at least once:

status changed FROM "Dev" TO "Testing"

This query will show you the list of tickets, though it won’t specify the exact number of transitions for each ticket.

Alternative Solution:
For a detailed report showing how many times each ticket has transitioned between “Dev” and “Testing” our app, Timepiece - Time in Status for Jira, the oldest and leading 'Time in Status' app in the Atlassian Marketplace, which is developed by my team at OBSS, 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.

If you prefer to export the data, Timepiece also supports exporting these detailed reports (including backward transitions) in CSV format for further analysis.

In addition you can 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! If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem