Docs / Configure
Automations
Rules that act on project events, for example updating a parent's status when all its stories are done. Triggers can be filtered by status, and each rule keeps a log of its recent runs.
When to use it
When you keep doing the same follow-up by hand.
Start here
Open the "Templates" tab, find a rule that fits and click "Add to Project". Or build your own from "Active Rules".
How to use it
- Open the "Templates" tab to see ready-made rules. Each card shows its trigger under "When" and its action under "Then".
- Click "Add to Project" on a card. The rule is created as active and you are taken to the "Active Rules" tab.
- To build your own rule, click "Add Rule" at the top right to open "Create Automation Rule". Enter a "Rule Name" and, if you like, a description.
- Choose a "Trigger", then fill in the "Trigger Conditions" that appear: From Status and To Status (blank means any), "Days Ahead" (1 to 90) for a milestone, or "Decision" for an approval.
- Choose an "Action", then fill in the "Action Configuration": for a notification pick "Send To" and a title and body, for an approval request pick a workflow.
- Leave "Enable rule immediately" on to start it now, or turn it off, then click "Create Rule". A rejected rule shows the reason in the dialog.
- On the "Active Rules" tab, use the switch to enable or disable a rule, the pencil to edit it and the bin to delete it after confirming.
- Click "Recent runs" on a rule to see each run as Done, Skipped or Failed, with the reason and the time.
Good to know
- Triggers: a story's status changes, is assigned or is created; an epic's status changes; all stories in an epic are done; a milestone is due soon; an approval is fully decided; a timesheet is submitted. Conditions filter without regard to case.
- Moving a card on the Kanban board or saving a story in its edit dialog does not run rules yet. Status and assignment rules run when the change is made through the story status and assign endpoints.
- Update parent status sets the epic once all its stories are done, or the feature once all its epics are done. Post a comment works on stories, epics and features. Create approval request needs a trigger other than "Approval is decided".
- A notification goes to the person who triggered the event unless "Send To" says otherwise; rules started by the schedule go to the project owner. Milestones are checked daily at 06:00 UTC and alert once per target date.
- Rules that were switched off when automations were updated show a banner and a "Paused by update" chip. Review each one, then use its switch or "Re-enable all".
Related
Last updated 6 October 2026