Jira Ticket Transition Report

Question

Hi There, Can you please help me to understand on reporting of a Jira ticket, which will show how the Jira ticket was transited on various status. e.g. We have status like Backlog->In Progress->Re test->Done Backlog<-In Progress<-Re test<-Done I want transition report between Re-test->In progress which is backward movement here. This will allow me to understand which tickets are fix by developer but in testing it gets failed and assigned back to In progress. Report should contain basic information of those backward moved Jira tickets. Let me know if required more information on the same. Regards Somnath

Valeriia_Havrylenko_SaaSJet · Answer

Hello @somnath.yadav 👋

Hope you found the answer!

Zoryana Bohutska _SaaSJet_ · Answer

Hi @somnath.yadav

For this case, you can consider also Issue History app. It will show you all status transitions, including information on when and who moved issues from one status to others.

You can see what sets you should make in column manager in the screenshot below (choose issue key, summary, and status fields).

Additionally, this add-on can show you all historical data about any issue updates (assignee changing, summary editions, all added comments, etc.)

Best Regards

Zoryana

Emre Toptancı [OBSS] · Answer

Hello @somnath.yadav ,

If you need to only see WHICH issues were reopened, you can use a JQL query like @John Funk recommended. If you need to see HOW MANY times issues were reopened or find issues that were reopened the most, you will need to track reopen count. You can do this by configuration or by using an app.

For configuration, you can create a custom number field (for each transition you are interested in tracking), modify your workflow and use a post function (provided by a marketplace app) in the said transition to increase the value of the new number custom field by 1. This way, the field will always hold the number of reopens (or whatever transition you are interested in tracking). This solution is viable for small use cases but for if you want to track multiple transitions, it requires a lot of workflow modification, it is hard to maintain. This solution also can only create reports after you make those modifications.

As an alternative, you can use a marketplace app built for this purpose.

For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status or assigned to each assignee but it also has reports that show Status Use Count and Transition Use Count for each issue. You can also calculate averages and sums of those counts grouped by issue fields you select. (For example average reopen count for assignee)

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.

Using Time in Status you can:

* See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
* Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
* Export your data as XLS, XLSX or CSV.
* Access data via REST API. (for integrations)
* Visualize data with various chart types.
* See Time in Status reports on Jira Dashboard gadgets (released for cloud, server&DC gadget coming soon)

Timepiece - Time in Status for Jira

Emre