Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

JQL to search members of "Request participants" custom field created by JIRA Service Desk

What would be the JQL to search for members of the "Request participants" custom field that it's created after enabling the JIRA Service Desk add-on

3 answers

1 accepted

4 votes
Answer accepted

Are you trying to find a list of all users who have ever been listed as Request participants? You could use JQL along the lines of the following:

"Request participants" is not EMPTY

Then you could modify which columns are visible so that the various Request participants are in front of you.

You can treat the Request participants field as you would other user fields, e.g. by searching for issues where Request participants are members of the administrators group:

"Request participants" in membersOf("administrators")

Request participants must also already be customers in your Service Desk. But I'm not sure exactly what you're trying to solve – if this doesn't help, could you clarify?

Hi, I'm currently struggling with the JQL query for a scheduled automation, I wanted to search issue that doesn't have the specified Request Participants, do perhaps know how to implement it? My automation rule is like this:

When scheduled run every friday
JQL is issuetype = X AND status in (A, B, C) AND ("Request participants" not in (CodeNameX) OR "Request participants" not in (CodeNameY))

My concern is that this condition reads all the past tickets which will throttle the automation if run since 10000 issues where found.

Came across this post looking for the Cloud answer. Which I posted here.

0 votes
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

Try the following:

username/assignee/reporter in "Request participants"

No. that doesn't work.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

What exactly you tried? And what is the error?

Operator 'in' does not support the non-list value '"Request participants"' for field 'assignee'.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

Oh ok. I haven't seen that custom field before but just wanted to give it a try! Sorry it didn't work.

Rodolfo Romero
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

No problem. You should have notice that this is a JIRA Service Desk question and anyone familiar with this add-on would know about this custom field. ;)

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

It is funny because we use the add-on and don't see the custom field. We are using the server version though!

Rodolfo Romero
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 02, 2015

I just checked the Release Notes and it seems this feature hasn't made it yet to the Server version. It's only available in Cloud. It's a great feature that allows you to share JIRA Service Desk features with other members of the organization through the Customer Portal.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events