You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
i need to make an automation rule based on a request participant.
an issue is created via email. the address is an alias. the address is populated into the request participants.
the rule is attached:
the triggers works, but the comparison fails.
any thoughts?
thanks
Hi @Ben
Request participants are displayed with names and not emails. Try using their names.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When the issue is created, the request participant field shows the email address not a user name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oook. But you do understand that I've just pasted an image that my rule worked, right?
Can you paste where exactly you select the request participant, when the issue is created? Maybe this will help me identify the possible cause, which to me the rule works, but it fails in your instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes, it was clear that your rule worked.
the request participants are set by email. just as you create an email based request with a CC, then the CC becomes the request participant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After your trigger add a Re-fetch issue data component. You have to do this, because when the issue is created, the log of Request Participant returns as EMPTY.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've added a Log after the trigger to capture the value of request participants. It seems that CCs are added as request participants in a later stage, after email creation. Confusing, I know, but that's what's happening :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anytime dude!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your comment here is super helpful. Knowing that email CCs are added as request participants in a later stage after email creation, how will I be able to to create an IF condition based on request participants? Because when the automation is triggered, request participants are always empty, so the condition will never be met. I tried "re-fetch issue data" but still no luck getting the condition .
Is there some sort of delay I can add here to make sure request participants are in place when the automation checks the IF condition?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Evan Yao re-fetch the data right after the trigger. Do that and let me know if that worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alex Koxaras _Relational_ I have an alias alias1@email.com to alias@email.com.
I need to add alias1@email.com as a request participant when the issue is created via alias1 and then route it to the respective queue.
The request participant field is always empty even added a refetch of the data right after the issue creation trigger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ahmar Mahmood create a new post please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need to apply the same automation to a "Cascade Option" field that is not yet available in the Automation.
It is only available in Legacy automation for now.
Anyone knows if it is possible to write a condition in JQL that would be the same as
"Request particpants contains any of [insert list of request parcipants]".
I am not convinced that the following JQL will act as "contains any of" and may act as "request participants are EXACTLY either user1, user2 or user3" :
"Request participants" in (User1, User2, User3)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.