Edits to issue do not update smart values later in automation rule.

[Max Chippington Derrick]

I have an automation rule that, upon creation of an issue, depending on one of the input fields, then updates the list of request participants. (Basically using it as a kind of automated triage.)

This works fine, however, in the same rule, I then make use of this list of request participants for email notifications, which I would expect it to be able to do, however, when I do so, any use of the request participants field uses the previous empty list; presumably as the changes do not get applied until the automation has finished.

Is there a way to change this behaviour?
Is there some alternative thing I should be using here?
And if not; is there a better workaround than having a second automation rule that gets triggered by the first (with all the extra debugging that incurs)?

[Marco Brundel · Accepted solution]

Hey,
Have you tried adding "Re-fetch issue data" action?

greetings, Marco

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/

[Max Chippington Derrick]

Aha, that's exactly what I need, thank you!