When-then rules with a dropdown builder and template gallery.
Tenant-defined automation rules. Every audit event (task.created, task.status_changed, comment.created, etc.) is matched against active rules; matching rules run actions (set field, apply label, notify user, call webhook). The v2 builder is dropdown-driven end-to-end - no typing of field names or event strings.
Why can only certain fields be set by set_field?
Automations bypass most guardrails to stay fast. The whitelist (status/priority/title/description/dueOn/startsOn on Task; status/name/ownerId on Project) is what we verified is safe to let rules write. Everything else needs the regular API path so its own validations run.
Can I edit a template?
Create from a template, then edit the resulting rule like any other - the template is a construction aid, not a runtime link.