Automations
Automate repetitive workflows with trigger-condition-action rules.
How Automations Work
An automation rule has three parts:
- Trigger — the event that starts the automation (e.g., issue created, status changed)
- Conditions — optional filters that must be true (e.g., priority is High)
- Actions — what happens when the trigger fires and conditions are met
Creating an Automation
Go to Settings → Automations and click New Automation. The visual builder lets you configure each part with dropdowns:
1
Choose a trigger
Select when the automation should run (e.g., “When an issue is created”).
2
Add conditions (optional)
Filter which issues trigger the automation (e.g., “Priority is Urgent”).
3
Define actions
Choose what happens (e.g., “Assign to @alice” and “Add label bug”).
Available Actions
| Action | Description |
|---|---|
update_field | Change a field value (status, priority, etc.) |
add_label | Add a label to the issue |
remove_label | Remove a label from the issue |
assign | Assign the issue to a team member |
set_status | Change the issue status |
notify | Send a notification to a user |
move_to_project | Add the issue to a project |
Examples
Auto-assign urgent bugs
Trigger: Issue created
Condition: Priority is Urgent AND label is “bug”
Action: Assign to on-call engineer
Move done issues to archive project
Trigger: Status changed to Done
Action: Move to “Archive” project