How can I count the number of times a ticket went to a certain status using JQL?

[Divjyot Puri]

I want to compare the performance of the developers in my team and for that, I need a query that can tell me the count(number of times a ticket was moved to Testing Failed status) and sort it by development owners

I have tried this query:

project = XYZ AND status changed FROM "Testing In Progress" TO "Testing Failed" AND "Development Owner" in (5e37dd74,5e43d7,5ef99583,5ee9d) ORDER BY "Development Owner"

But I am not able to achieve what I want. Please help.

Thanks!

[Andrew Laden]

This is a common misconception with JQL. it is not a full query language like SQL. It can only ever produce a list of issues. You can't use it to produce a tally or any other calculated value.

What you will need is a field in the issue that can track the number of times an issue has passed through a transition. ie

1. Make a new Number Field custom field - Call it Count of failed tests.
2. For every transition that can go to "Testing Failed" as a post function to increment that field by 1. (how you do this will depend on what Addons you have)

You can then use that field as a sort value in your JQL to produce a sorted list of issues.

There are also addons that can measure it for you. For exmaple.

https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview

[Mehmet A _Bloompeak_]

Hi @Divjyot Puri ,

You can try below apps. They provide status count report as well as various other status reports.

• Status Time
• Status Time Free

[Bill Sheboy]

Hi @Divjyot Puri 

However you choose to implement this idea, please consider that it may not indicate what you think it is measuring.

You asked about measuring the number of times a work item moves from "Testing In Progress" to "Testing Failed", which could happen for a variety of reasons:

• Failed test due to a development error
• Failed test due to a testing error
• Unclear request, leading development and testing skills people having a different understanding of the request
• Overzealous testing, beyond the scope of the requested work
• JIRA usage error, moving a work item to the wrong place on the board
• And so forth...

Perhaps your team could consider each occurrence as a chance to learn and improve, rather than as a means to assume the people's performance.

Best regards,

Bill

[Zoryana Bohutska _SaaSJet_]

Hi @Divjyot Puri 

Also, you can consider another tool from the Atlassian marketplace. It lets you monitor data about the number of times a ticket went to a certain and moved from one status to another.

Regards