I need to see list of issues where status changed back from IN QC, Ready for UAT to IN progress.

Question

I have checked various posts already here, and tried using

project = "ABC" and status changed FROM "IN QC" TO "In Progress" and status ="In Progress"

But its missing out issues which I have transitioned.

-- Does the query check only for first transition?

For ex -

Issue ABC-75 moved from Backlog to In QC, Then moved back to In Progress

When I query it like:

project = "ABC" and status = "In Progress" AND status WAS Backlog ORDER BY created DESC

I get to see my issue ABC-75 in the list

But when I do ,

project = "ABC" and status = "In Progress" AND status WAS "In QC" ORDER BY created DESC, This issue ABC-75 is not showing up

Mehmet A _Bloompeak_ · Answer

Hi @Saloni Goel ,

"status changed" query checks all the transitions, but it matches the direct transitions. That is, if an issue was moved from "IN QC" to "Ready for UAT" and then to "In Progress", the query "status changed from INQC  to InProgress" will not list the issue.

I guess below query should work in your case.

project=ABC AND
(status changed from "IN QC" to "In Progress" OR status changed from "Ready for UAT" to "In Progress")

Karolina Wons_SaaSJet · Answer

You can try a demo version as well.

Hope it fits your needs.

Emre Toptancı [OBSS] · Answer

Hello @Saloni Goel

The "status changed" operation checks the whole issue history. You should even be able to use multiple instances of that operator. I mean, the following is a perfectly valid query:

project = "ABC" and status ="In Progress" and (status changed FROM "Backlog" TO "In QC") and (status changed FROM "IN QC" TO "In Progress")

This query translates: Get me the issues

* That are in ABC project
* That are currently in "In Progress" status
* That were transitioned from Backlog to In QC, sometime in their histories. 
* That were transitioned from In QC to In Progress, sometime in their histories.

Please note that the "status changed" operations are independent. That means it doesn't matter in which order you use them. Each one scans the issue transition history separately.

Hope this makes sense.

Using a marketplace app for this will probably make things much easier to report. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira 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 and on each assignee.

The app also has Status Count and Transition Count reports that show how many times each status and each transition was used. This is exactly what you are looking for.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

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. It supports both Company Managed and Team Managed projects.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

And the app has a REST API so you can get the reports from Jira UI or via REST.

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 issue type.)
* 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

Timepiece - Time in Status for Jira

EmreT