Switch-Style Branching in Rules?

Would it be possible to add a “switch” style branching option to Asana Rules, rather than only supporting “if condition” branches?

There are scenarios where a single trigger should result in multiple independent conditions being evaluated. Ideally, the rule would evaluate every matching condition and execute all corresponding actions, rather than stopping after the first matching branch.

For example, instead of it checking the first branch and only proceeding to the next if the first branch isn’t met likeso:

Trigger: A field is updated

  • If Condition A is true → Perform Action A
  • Else if Condition B is true → Perform Action B
  • Else if Condition C is true → Perform Action C

What I want is for it to go through all the branches so that it runs all the necessary actions that meet the condition.

Trigger: A field is updated

  • If Condition A is true → Perform Action A
  • If Condition B is true → Perform Action B
  • If Condition C is true → Perform Action C

I worry that I might reach the rule limit in a project soon with the number of possible conditions I need to account for

Would it work if you added a second rule for B and a third rule for C?

Yes, thanks, this is the workaround we have in place for the meantime - One rule per condition. I do worry that this may grow and reach the limit of rules allowed in a project. But we might have to just cross the bridge when we get there

@Katrina_Madamba I know this isn’t ideal, but one workaround is to increase the number of rules by multihoming. This can be especially useful if you’re applying the same rule actions across multiple projects.

For example, I have a dedicated Rule project set up to apply a specific set of rules to anything that is multihomed to it. Once the rules have been applied, the task is automatically removed from the Rule project.

So, instead of having three separate rules for Conditions A, B, and C, you could have one rule that says:

If the field is changed → Add the task to the “Rules” project.

Then, in the Rules project:

  • If Condition A is true → Perform Action A and remove the task from the Rules project.
  • If Condition B is true → Perform Action B and remove the task from the Rules project.
  • If Condition C is true → Perform Action C and remove the task from the Rules project.

This essentially lets the Rules project act as a centralized automation hub while keeping the rules themselves out of the original project.

I recognize this won’t work for every action, but it gives you something to think about!