Automation to check assignee does not seem to be executing in order

Greg Jas

I have an automation that assigns a ticket to an agent based on customer organization. I added in a check after the agent is assigned against a group of users on vacation. This check doesnt work as expected and returns the users doesnt fit the criteria in the audit log even though the user assigned in the previous step is in the group. Below is a picture of this section of the automation. Is there something I'm doing wrong? Is the check too fast after the assign that it doesnt see the new user?

I've also tried using a 2nd automation triggered by a change in the Assignee field but it does not reliably trigger.

 

Basically this would then loop back into another automation to assign the ticket to a group of users until the assignee is not in this vacation group 

Bill Sheboy

Hi @Greg Jas -- Welcome to the Atlassian Community!

The steps in a rule use the current state / data in the issue which the rule holds.  And when an edit happens (e.g., Edit Issue) that updates the data in the cloud but not the rule's storage.  This is by design to help with conditions, etc.

When you want the rule to use the updated information, add the Re-fetch Issue action after the change, such as after your Edit Issue action and before the condition:

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data

That will reload the data before the rule proceeds.

Please use this action only when necessary as it will add about a second of time to the rule execution.

Kind regards,
Bill