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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,905
Community Members
 
Community Events
176
Community Groups

Jira cloud automation user condition: Initiator is one of request participants

Hello,

in Jira Service Management Cloud Automation I need a (kind of) user condition to check whether the initiator is one of the request participants like this:

If INITIATOR is any of REQUEST PARTICIPANTS then ...

Not all request participants are customers, so I cannot use the customer condition.

Do you have an idea how to solve this?

Thanks :)

1 answer

1 accepted

3 votes
Answer accepted
Esther Strom Community Leader May 20, 2021

Hi, @Rebecca  - you can do this using the JQL condition with a smart value, rather than a user condition. 

Your condition would look like this:

2021-05-20 11_17_13-Project automation - Jira Staging - Vivaldi.png

Hi @Esther Strom, thank you very much for your quick help!!! This is exactly what I was looking for.

@Esther Strom isn't jql conditions performance-costly?

I think advanced compare condition would be more efficient

something like:

{{issue.customfield_14402}}

contains

{{initiator}}

Thank you Esther :)

Esther Strom Community Leader Nov 22, 2022

@DevRimantas yes, JQL can be resource hogs if you're doing intense processing or returning a ton of data, but I wouldn't think something simple like this would really cause much of a problem unless it's being run many times per second.

Like Tom Gardner likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events