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; } } }

Automation sending email to Request participant even though he has been removed earlier in the rule.

Tyler Giles

Hello!

Please see screenshot. I have an automation rule that is not working as expected. I want it to remove a specific user from 'Request participants', and then send an email to 'Request participants'. The removal works GREAT! (Edit issue field- Advanced). This does exactly what it is supposed to do.

But, the email below is still being sent to the user above, who was removed. This has nothing to do with Reporter, that is also working fine and is a different user all together. This was not working with out the delay, so I went ahead and added a 30 second delay, and it is still not working as expected. Removed user (who is 100% removed) is still getting email addressed to 'Request participants' of which they are no longer a part of.

Any ideas? Thank you so much for your time!

Accepted answers

Mikael Sandberg

The delay will not update the data the automation have about the issue that triggered the automation. If you do an edit of the issue within the automation, like in this case remove a user from the request participants field you have to Re-fetch issue data for it to work as you expect it.

All comments

Mikael Sandberg

Joseph Chung Yin

@Tyler Giles

I agreed with @Mikael Sandberg stated, you need to add an action "Refetch Issue Data" and place it right before your Send Mail action in your automation rule.

Best, Joseph Chung Yin

Tyler Giles

@Mikael Sandberg This worked perfectly, thank you!

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