Create Asana Project Rules
Use a rule for a repeated, deterministic routing action. Configure its trigger, conditions and effect explicitly, then test both matching and nonmatching tasks before publishing broadly.
Step-by-step guide
Check access and scope
Rule features depend on the plan and automation permissions. Identify the rule owner and check other rules affecting the same fields.
Choose one narrow trigger
Open Customize and the project automation or rules controls.
Define the trigger event
Choose one narrow trigger such as a field value change.
- Worked example: When Request type becomes Security review, assign the designated reviewer and move the task to Review. Do not let another rule move every new task straight to Approved.
Add limiting conditions
Add conditions that limit which tasks should be affected.
Choose the action
Configure the routing or property action.
Test matching and exception tasks
Test a matching task and an exception, then inspect execution behavior.
Verify the result
The matching task changes once as intended, while the exception retains its original owner and state.
Common mistakes
Check the handoff edge case
A rule owner who leaves without a handoff makes failures harder to investigate. Record the maintenance owner with the workflow.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.