Sequence of Automation Rules in a Space

Hello!

We have a few cases where a space / folder / project has more than one automation rule assigned to it, and the functionality of one is impacting the other as they are happening in the wrong order.

Please see below use-case scenario that illustrates the requirement:

We have a rule applied at the Space level where, Trigger = New Item Created, Conditons = Custom Fields are blank, Action = Add item to "Tasks with Blank Custom Fields" folder
We then have a rule applied to a Project (Top) within this space where, Trigger = New Item Created, Action = Populate Custom Fields as specified

Automation Rule #1 takes place first every time, so tasks that have Custom Fields populated are being tagged into the Blank Custom Fields folder when they have actually been populated.

Is there any way for us to specify the order in which automation rules take place so we can avoid this conflict?

Any feedback from Wrike Community Team or Community Members on how to achieve this would be greatly appreciated. Thanks so much.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Paul Calabro

Being able to set up a hierarchy of which Automation Rules take place would be very helpful and avoid conflicts for me too. Hope to see this feature added soon!

Melanie Mondon

Agree - this would be a very useful feature for us.

Elizaveta Bogdanova

Thanks a lot for sharing this idea @Jess Cuddy, and for supporting it, folks!

I checked with our team responsible for automation, and they don't currently have this on their roadmap due to other priorities. However, your feedback has been noted, and we'll let you know if we have changes for the order of the automation rules 👍

Marcelo Jucá

I have two rules (#1 and #2, created in this order) that impact the same field (Status) and depending on their priority, the result would be different. I guess the automation execute both as both pre-requisite are fulfilled, but the execution goes in this order: #1 and then #2. A workaround I found out was to duplicate the rule #1 (creating a rule #3), disabling/removing the #1 so the final result is the expected because it executed #2 and then #3. Is there any plans to define automation rules priority?

Rohan V

Hello @Marcelo Jucá, welcome to the Community, and thank you for sharing your workaround. Currently, there are no updates about the ability to set the priority or execution order of automation. We will keep you informed if there are any changes in the coming months 👍