Automations

Automations remove the busywork that surrounds real work: re-labeling, reassigning, moving states, posting to Slack. A rule is a trigger, optional conditions, and one or more actions — no code required.

Anatomy of a rule

A trigger fires on an event (an issue is created, a state changes, a PR is opened). Conditions narrow when the rule applies (only for the Support team, only when priority is Urgent). Actions are what happens (set state, assign, add a label, post a message).

When  an issue's linked PR is opened
If    the issue is in 'In Progress'
Then  set state to 'In Review'
      and notify the assignee in Slack

Destructive actions are gated

Bulk or destructive actions (bulk archive, bulk update, delete) go through a propose-then-approve path rather than firing silently, and each is recorded in the audit trail. The same guardrail applies whether the action comes from a rule, the API, or an AI agent — the rule of least surprise is enforced in one place.

Tips

Start with one rule that removes a clear, repetitive chore and watch it for a cycle before adding more. Over-automation is harder to debug than no automation. Every rule's runs are visible, so when something moves unexpectedly you can trace exactly which rule did it.