nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL query needed to filter out 'Done' tasks on the basis of who marked it as resolved

unknown

Hello.

I am in desperate need of a JQL query that could help me filter out the bugs that have been marked as DONE/RESOLVED but not by the QA.

We have some flaws in the bug workflow thus some developers are able to close the ticket without my knowledge which is impacting my quality of work in a negative way.

I am the only QA and want a JQL that helps me filter out DONE issues that have not been marked done by <My name>.

Such bugs have been assigned back to me so its difficult for me to open 1000+ bugs one by one to check if it was closed by me.

Kindly help me create a JQL.

Thanks!

Accepted answers

Sanjog Sigdel

Hello @[deleted] Welcome to the community.

I checked the JQL and columns. Currently there are only Approvers and Approvers Group but I found no assignee under Approvers.

But there is an workaround which you should do via automation:

Create a Custom field:- Approved By.
Make it available to all projects.
Create a Automation
1. Which Assigns the one who accepted the ticket in the Approved By Column
Then in your JQL you can get the Approved By column and also the person who approves the ticket.

Please try the automation and let me know when you have issue while implementing this.

Bill Sheboy

Hi @[deleted]

You note you are the only person doing QA work and there are 1000+ bugs to manage. I respectfully suggest having a conversation with your leaders and team about the situation as that seems unsustainably.

Back to your question...

How many other people are on the team who could be transitioning the issues?

If there are not too many, you could use JQL and the CHANGED operator to identify who is making the changes: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED

For example,

project = yourProjectName
 AND (
         status CHANGED BY userName1 TO Done
      OR status CHANGED BY userName2 TO Done
)

Where userName1 and userName2 are the other team members.

Kind regards,
Bill

All comments

Sanjog Sigdel

Hello @[deleted] Welcome to the community.

I checked the JQL and columns. Currently there are only Approvers and Approvers Group but I found no assignee under Approvers.

But there is an workaround which you should do via automation:

Create a Custom field:- Approved By.
Make it available to all projects.
Create a Automation
1. Which Assigns the one who accepted the ticket in the Approved By Column
Then in your JQL you can get the Approved By column and also the person who approves the ticket.

Please try the automation and let me know when you have issue while implementing this.

unknown

This is genius! Thank you so much for this suggestion. I'll be working on it and let you know once I achieve the above solution.

Thanks again!

Bill Sheboy

Hi @[deleted]

Back to your question...

How many other people are on the team who could be transitioning the issues?

If there are not too many, you could use JQL and the CHANGED operator to identify who is making the changes: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED

For example,

project = yourProjectName
 AND (
         status CHANGED BY userName1 TO Done
      OR status CHANGED BY userName2 TO Done
)

Where userName1 and userName2 are the other team members.

Kind regards,
Bill

unknown

Hi.

Thank you so much for this suggestion.

I tried it out with the usernames but it didn't work that way for me so I tried it with user ids and it did the job.

example :

project = "Projectname" AND ( status CHANGED BY user_id TO Done ) ORDER BY created DESC

So quick and easy.

Thank you so much!

PS: Yes, I've already had a word with my team leads and they'll be handling the matter now. Thank you for the concern!

Bill Sheboy

I am glad to learn that helped. After the changes a few years back to user information, I believe that most JQL operations now require using the account ID values.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

bug