We have some exciting news to share with you today! In May we launched inverse actions for Rules and today we’re very excited to share that we are introducing Rule chaining, the ability for Rules to trigger other Rules!
Rule chaining is designed to help you to reduce the manual effort needed to get your work done from start to finish. Going forward, you will be able to connect multiple Rules together and create a flow of information between more projects and teammates.
A couple of important notes:
Rule chaining is disabled for all existing rules.
You can enable rule chaining for existing rules following these steps:
Edit the rule you want to be triggered by other rules
Select the “…” icon in the top right corner
Check the box to allow the rule to be triggered by other rules
Save changes to rule
All new rules will have the rule chaining functionality enabled by default.
This feature is available to Premium, Business and Enterprise customers.
Example
Rule A: Status changed > Add to another project
Once the task is added to another project, it will automatically trigger Rule B.
Rule B: Tasks added to another project > Assign task
Hi there. It could be handy to have a tag for this announcements (od begin the post with businessenterprise) that this is in Business and Enterprise. I always read the news with joy to be finally disappointed this is not in my Premium plan
Hi @Christina_Harris1, welcome to the Asana Community Forum! As it stands, for Rules to apply to subtasks, you need to add the subtask to the project. We don’t have immediate plans to create a trigger to take an action on subtasks, I recommend you adding your vote to this thread and we will make sure to post updates as soon as we have any: Allow Rules for Subtasks
Thanks for your feedback, @Marek_Cevelicek! We will definitely start leveraging more the tags function in the forum to give more insights about the product updates.
Hello,
Rule chaining is great, and will certainly simplify our setup!
To take this one step further, it would be helpful to attach rules directly to custom fields, and would apply to any project that uses that custom field. While I don’t have access to the rule chaining feature to test this yet, I assume this can now be more-or-less accomplished by moving a task to a specific project to handle and apply a custom field rule, but it would be simpler to apply the rule to the custom field itself.
Will the number of rules allowed within projects be increased with this? We have a lot of rules currently and would love to see that if they’re chained together it would all be considered one rule.
@AdR you are right! With Rule chaining, when you move a task to another project a new action will be triggered automatically! The feature will be available to all customers soon so you can test it and ask any follow-up questions, apologies for the delay!
Great question, @Amy_Inman! I’m afraid we are not increasing the number of Rules you can have per project. Each Rule will count as one separate rule even if it will trigger another rule with the new chaining feature. I recommend you voting for this request here: Increase limit of 20 rules per project.
Hi everyone! Rule Chaining is now available to all customers
Our product team also confirmed this feature is available to Premium customers too. I have updated the post as I had mentioned it was only available to Business and Enterprise before
So happy to see the recent improvements to the Rules i.e. inversion rules, and chaining. Are there plans to incorporate more boolean logic, such as If this and not that, or If this and that or this and that then… Also any plans to give priorities to rules, for instance run these rules in a specific sequence. I have some rules that are very close to each other, and I believe that they may be canceling one of them and would love to be able to tell the system to check this rule before moving on, if it applies run it, if not move on to the next rule.
Want to be automatically notified of all new upcoming product updates? Make sure to follow our Announcement category!
