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,298,560
Community Members
 
Community Events
165
Community Groups

automation condition o request participant.

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:

2021-10-15 14_34_07-Project automation - JIRA.png

 

the triggers works, but the comparison fails. 

any thoughts?

 

thanks

 

1 answer

1 accepted

3 votes
Answer accepted
Alex Koxaras Community Leader Oct 15, 2021

Hi @Ben 

Request participants are displayed with names and not emails. Try using their names.

Alex Koxaras Community Leader Oct 15, 2021

req participants.png

When the issue is created, the request participant field shows the email address not a user name.

Alex Koxaras Community Leader Oct 15, 2021

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.

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. 

Like Alex Koxaras likes this
Alex Koxaras Community Leader Oct 15, 2021

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.

yes! that worked :)

Thank you!

How did you realize that?

Like Alex Koxaras likes this
Alex Koxaras Community Leader Oct 15, 2021

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 :/

neat trick :) i'll keep that in mind.

thanks for looking into this and helping out!

Like Alex Koxaras likes this
Alex Koxaras Community Leader Oct 15, 2021

Anytime dude!

Hi @Alex Koxaras 

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!  

 

 

image.png

Alex Koxaras Community Leader Jan 23, 2022

@Evan Yao re-fetch the data right after the trigger. Do that and let me know if that worked.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Coming Soon: Insight Changing to Assets

The 2020 acquisition of Mindville added powerful asset and configuration management capabilities to Jira Service Management in the form of Insight. Following the completion of that integration, custo...

294 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you