how to assign order of operations for automations?

Greg Pekrul
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!
December 3, 2024

I'm trying to add and remove members when moving from one list to another. I would like to auto assign on the first list when a card is created, then move the card to the next list, where current members would be removed and different members would be assigned. When i try to remove everyone on the card then assign new members both by the automations, the software adds the new members first then removes everyone. I would like to remove members as they left the list, as logic the states, then add new members in the list that the card is moved into. 

Remove first then add, not add members then remove everyone. 

1 answer

1 accepted

1 vote
Answer accepted
Renato Fagaraz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 5, 2024

Hi @Greg Pekrul !

It sounds like you're trying to get your Trello automations to do a bit of choreography with your team members on the cards hahahahaha. Here's the thing:

If you're using the same trigger for your automation (like "when a card is moved to a list"), you can absolutely queue up your actions in the order you want them to happen. Just go into your automation setup and make sure you've got the actions lined up in the sequence you prefer. So, put the "remove members" action first, followed by the "add X member" action. Trello will follow that order when executing the automation. Something like this:
image.png

However, if you've got two different automations being triggered by your workflow (like one automation for removing members and another for adding them), then it's a bit of a wild card. Both automations will try to run at the same time, and there's no guarantee which one will finish first. In that case, you might need to consolidate your actions into a single automation to control the order.

Hope that helps! 😊

Greg Pekrul
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!
December 5, 2024

That makes sense. I'm not sure why i was trying to separate the automations, instead of one trigger for all actions. 

 

Thank you, this is exactly what i needed.

Like • Renato Fagaraz likes this

Suggest an answer

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

Atlassian Community Events