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 filter by requests participants not working

Nahuel Logghe

I'm trying to find all the issues from one organization where a specific user is NOT listed as a request participant.

I'm currently using this query:

project = PJ1 AND Organizations = "Organization AS" AND "Request participants" != "User A"

However, it's returning 0 issues. When I remove the "Request participants" condition and only search within the organization, I do get several issues where the user isn't listed as a participant. I've also tried NOT IN and IS NOT instead of != with the same results.

Do you have any suggestions on how I can adjust the query to get the correct results?

Thank you!

Accepted answers

All comments

Christopher Yen

Hi @Nahuel Logghe

Any chance the individual is deactivated? I know I've had some difficulties with searches regarding deactivated accounts.

I tried != and not in and both seem to work at least in my instance.

"Request participants" != "Chris Yen"

("Request participants" not in ("Chris Yen"))

Mark Higgins

hi @Nahuel Logghe

Just looking to reproduce your issue on my site.

So I started with a straight query of 'Request participants" is not EMPTY

Screenshot 2024-08-22 085059.png

Then I changed it , so that it does not grab MarkProject.

Screenshot 2024-08-22 085228.png

Which worked as expected?

It could be other parts of your query around Project and Organisation that is causing the result you are getting.

Hope this helps.

Regards

Mark

Nahuel Logghe

Hi @Mark Higgins Thank you for your response. Your explanation helped me understand that each parameter works correctly when used on its own. For example, you can filter by "Request Participant" without also filtering by "Organization" or "Project." Similarly, you can filter by "Organization" without involving a "Request Participant."

Interestingly, it seems to function properly (although I'm not 100% sure if it's showing all the results) when you filter by '"Request Participants" ='.

However, when you try to use '"Request Participants" !=' in combination with both "Project" and "Organization," it returns inconsistent results.

I'm really lost here, it makes no sense to me the different behavior.

Nahuel Logghe

Hi @Christopher Yen

The user is active. I also tested with different users. Basically , what I just told Mark in the previous message. It seems to work when only looking by Request Participants, but it gets wrong results when looking for negative results (!=) and combining it with more parameters.

Mark Higgins

hi @Nahuel Logghe

I've created a few more tickets in my test system, because I am curious to understand.

So, the statement != Request Participants, appears to work for both = Projects and != Projects.

Screenshot 2024-08-23 114219.png

Screenshot 2024-08-23 114350.png

Just confirming the consistency of numbers.

My Project "IT Operations" has: 5206 issues.

Total where Request Participants is empty = 5101

Total where Request Participans is not empty = 105

So on my project the results are consistant.

Replicating your query:

project = PJ1 AND Organizations = "Organization AS" AND "Request participants" != "User A"

I tried putting my name in quotes, and it happily returned the results I expected:

Screenshot 2024-08-23 115449.png

Screenshot 2024-08-23 115601.png

So its consistent using my name or Atlassian ID.

Do you need to expand your query to include "Request Particpants" is not EMPTY?

Let me know.

Thanks

mark

Nahuel Logghe

Hi Mark,

It doesn't work for me when searching by project, organization, and request participant. In the end, I just looked by project and organization and manually searched the issues I needed.

Jeffrey Luke Brunett

A project manager in my organization recommended using "assignee was in (user1, user2, ...)" to replace the previous "participants in (user1, user2, ...)" JIRA issue search function. Seems to work okay for our purposes. Godspeed!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management