Order of automation actions

In 1 automation rule, I want to send a message to the current assignee and after that, change the assignee. But automation bot first changes the assignee and then sends the message.. The automation seems to ignore the order in which I add the actions.. Can this be solved?

 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
8 comentários

Karen Reijneveld can you post a screen capture of your rule?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Melissa,

The first screenshot is from the behaviour I saw yesterday. Currently the setting are like the second screenshot. Just now, I tried again and to my surprise it now works in the correct order...!?!  I may have changed the position of the item 'Change item status to'. But I am sure that the comment was before the assignee all the time. I have no idea why it is diferent now, but it seems to work....

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Karen Reijneveld, thank you for bringing this to our attention 👍 Please, let us know if you still need assistance with this.

Melissa Gallo thank you for helping here! 

Juan Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Juan Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Juan I think we need assistence with this. The text in my second post was incorrect and you can see that in the screenshots. It should:

  1. add comment
  2. change status
  3. change assignee

But it:

  1. reassigns
  2. comments
  3. changes status
0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Karen Reijneveld, thank you for the follow-up. I have opened a ticket with our Support Team and one of our agents will contact you shortly to assist you with this 👍

Juan Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Juan Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Juan,

The support team unfortunately told me: "I am afraid, at the moment there's no way to set up the exact order for the actions to take place, so it won't be possible to make sure that the initial assignee is @mentioned, then the status is changed, and only then the new assignee is added. It would take at least 2 rules to achieve for such a scenario. So as a workaround, one could think of how to modify the existing rule or create an additional rule."

Karen

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thanks for the update Karen Reijneveld and for sharing here. Will this workaround address your use case, or would you like me to move your request over to our Product feedback forum as a new suggestion? 

Elaine Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Elaine Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Elaine I would like to see this as a suggestion for the Product team. Right now I have a space with 2 pieces of automation and I need one to be an "always" and one to be dependent on the other. My example - I have 1 automation to say if any child task fails the parent task is moved to fail. Then I have another automation that says if any child task gets moved to "active" change the parent to active. So child task 1 fails - parent task is moved to fail. Child task 2 is changed to active - parent task gets changed from Fail to Active. But I need Fail to be the priority - if ANY child task fails the parent task fails.  I can do a work around for priority and make the automation more complex but being able to number the automation in terms of priority would be AWESOME.

 

 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Order of automation actions
[this list is visible for admins and agents only]

Alto
Didn’t find what you were looking for? Write new post