Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - adding approvers within a "For AQL" branch yields unexpected results

Malcolm Rogers
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 22, 2025

Hello all. I am trying to automate dynamically adding approvers to a task but the order of operations within the branching logic is preventing it from working consistently. Due to other factors within our environment, I am pulling user information out of Assets when adding approvers. I pull these users into an object in the For AQL statement, then use an Edit Work Item step to update the Approvers field, which is a multi-user select field. It seems that this branch is not working sequentially, as it seems random who the approvers end up being.

Clipboard_08-22-2025_01.jpg

I added the "Re-fetch work item" step in an attempt to work around this and hopefully force it to wait for the edit step to finish. You can see in the Activity that the updates happen "out of sync".

Screenshot 2025-08-22 101651.jpg

I know that you can use an Approval Group, but that will not work for us due to various circumstances.

Anyone have any ideas of what I can do differently to get this field set properly? Thank you!

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events