I appreciate the new conditional logic that is provided by Asana for rules, namely “ALL” triggers happen, or “ANY” triggers happen. There is a lot of limitation to these “conditions”, and what would make these rules MUCH more flexible is if there was conditional logic based on the task’s CURRENT STATE.
Below I’m going to express different options available to select between parenthesis( )
For example, a setting where rules should (ONLY, or NOT) activate if:
- Task’s Custom Field (EQUALS, DOES NOT EQUAL, CONTAINS) “____________” (multiple options selectable for multi-select field-types)
- Task (IS IN, IS NOT IN) Section “_________”
- Task’s Due Date Field (IS, IS BEFORE, IS AFTER, IS BETWEEN) “__________”
- Task’s Assignee Field (IS, IS NOT)
- Task’s Completion Status (IS, IS NOT) “__________”
- Task’s Creation Date (IS, IS BEFORE, IS AFTER, IS BETWEEN) “_________”
- Task (IS, IS NOT) in Project(s) “________”
Etc.
This would enable rules to be much more customizable to each user’s use case, and allow custom workflows that would stop rules from affecting ALL TASKS IN A PROJECT (huge limitation), and would only affect rules matching the conditional rules. It’s currently a huge limitation that rules only affect tasks that have had a STATE CHANGE. I know it would be possible resource-heavy to have rules activate based on a current state, but maybe that poll could be a fairly long poll (every 5 minutes) instead of instantly, per se to reduce server demand