Automations

Automations let you define rules that automatically update tasks when specific events occur. Instead of manually changing task fields after every status update or assignment, automations handle it for you.

What is an Automation Rule?

An automation rule has two parts:

1. Trigger (When) — The event that fires the rule
2. Action (Then) — What happens automatically when the trigger fires

For example: "When a task's status changes from Todo to In Progress, automatically set priority to High."

Accessing Automations

1. Navigate to a project within a team
2. Click the Automations tab in the project header

Available Triggers

Trigger Conditions

Some triggers support optional conditions to narrow when they fire:

Status Changed:

• From Status — Only fire when changing FROM this status (e.g., "todo")
• To Status — Only fire when changing TO this status (e.g., "inprogress")
• Leave blank to fire on any status change

Assignee Changed:

• To Assignee — Only fire when assigned to a specific person
• Leave blank to fire on any assignment change

Available Actions

Creating an Automation Rule

1. Click the Automations tab on your project
2. Click New Rule
3. Fill in:
   • Name — A clear name describing what the rule does (e.g., "Auto-assign on review")
   • Description (optional) — More detail about the rule's purpose
   • When (Trigger) — Select the trigger type
   • Then (Action) — Select the action type
   • Configure trigger conditions and action values as needed
4. Click Create

The rule is created in an enabled state and starts firing immediately.

Enabling and Disabling Rules

Each automation has a toggle switch. Click it to enable or disable the rule:

• Enabled — The rule fires when its trigger occurs
• Disabled — The rule is saved but does not fire

Disabling a rule is useful for temporarily pausing it without deleting the configuration.

Viewing Execution Logs

Every time an automation fires, it logs the execution:

1. Click the three-dot menu on any automation card
2. Select View Logs
3. See a list of executions showing:
   • Result — Success or Error
   • Task — Which task triggered the rule
   • Date — When it fired
   • Error message — If the execution failed, why

Logs are kept for the last 50 executions per rule.

Deleting a Rule

1. Click the three-dot menu on the automation card
2. Select Delete
3. The rule and its logs are permanently removed

Example Automations

Here are common automation patterns:

Auto-assign on status change

• Trigger: Status Changed, To: "inreview"
• Action: Set Assignee to your QA lead
• Effect: When anyone moves a task to "In Review", it's automatically assigned to the reviewer

Auto-tag completed tasks

• Trigger: Task Completed
• Action: Add Tag "shipped"
• Effect: All completed tasks get a "shipped" tag for easy filtering

Priority escalation

• Trigger: Status Changed, From: "todo", To: "inprogress"
• Action: Set Priority to High
• Effect: Tasks that move to active work automatically get elevated priority

Status cascade

• Trigger: Assignee Changed
• Action: Set Status to "inprogress"
• Effect: When a task is assigned to someone, it automatically moves to "In Progress"

How Automations Execute

• Automations run after a task update is saved
• They execute in the order they were created
• Multiple rules can fire from the same event
• Execution is fire-and-forget — it does not block the task update response
• If an action fails, the error is logged but the original task update still succeeds

Tips

• Start simple — Begin with one or two rules and expand as you learn what works
• Check logs regularly — Review execution logs to make sure rules are firing as expected
• Disable before deleting — If unsure about a rule, disable it first to see if your workflow still works
• Avoid circular rules — Don't create rules where the action triggers another rule that triggers the first (e.g., status change setting status)
• Name rules clearly — Good names make it easy to understand what each rule does at a glance