Stop doing the same manual task updates over and over. Create rules that trigger automatically when things happen in your workspace — assign tasks, move statuses, notify the right people, set due dates. Your team focuses on work; the automation handles the process.
Plain-language rule builder — no code, no YAML, no developer needed.
Automations start with a trigger — the event that fires the rule. Available triggers include: task created, task status changed, task assigned, task due date approaching (X days before), task overdue, label added or removed, comment added, checklist item completed, and milestone reached. Each trigger can be scoped to a specific project, label, or status value.
Add conditions to make a rule more precise — "only run this automation if the task has label X" or "only if the assignee is in team Y" or "only if the task is in project Z". Conditions are AND/OR combinations of any task field, custom field, or metadata. Without conditions, a trigger applies to everything that matches; with conditions, you narrow it to exactly the right subset.
The "then do this" part of the rule. Available actions: change status, assign to a specific person or round-robin, set due date (fixed or relative), add or remove a label, move to a different project, create a subtask, send a notification to a member or channel, and log a comment on the task. Chain multiple actions in one rule — "when status changes to Review: assign to Sarah AND notify the #design channel AND set due date to 2 days from now."
Start from a library of pre-built automation templates for the most common use cases: sprint close-out, new task assignment routing, due date notifications, blocked task escalation, and more. Browse, preview, and activate a template in one click — then customize the trigger conditions and actions to fit your exact workflow.
The most impactful rules teams set up in their first week.
Route newly created tasks to the right person automatically based on label, project, or type. Use round-robin assignment to distribute tasks evenly across a support or QA team — no manual balancing. When a task is moved to a "Review" status, auto-assign it to the designated reviewer for that project. Unassigned tasks in your queue go to zero.
When all subtasks of a parent task are complete, automatically mark the parent as done. When a blocked task's dependency is resolved, move it from "Blocked" to "Ready". When a task is approved in review, automatically move it to "Done" and archive it. Status cascades eliminate the manual cleanup work after meaningful events happen in a project.
Send a notification to the assignee 2 days before a task is due — a heads-up while there's still time. Notify the project manager when any task in the project becomes overdue. Escalate to a channel if a critical-priority task hasn't moved status in 48 hours. Turn deadline anxiety into proactive alerting that keeps everyone ahead of the deadline.
Every automation execution is logged — which rule fired, which task it affected, which actions were taken, and at what timestamp. When something unexpected happens to a task, the automation log shows exactly which rule caused it. Rules can be temporarily disabled for debugging without deleting them. Export the log for compliance or audit purposes.
Pick the event that should start the automation — task created, status changed, due date approaching, label added, or a dozen other options. Scope it to a project or the whole workspace.
Narrow when the rule fires with conditions on any task field. Without conditions it applies broadly; with them, it applies precisely to the tasks that match your criteria.
Choose one or more actions to execute — assign, change status, notify, set due date, add label, create a subtask. Save and the rule is live. Monitor it in the automation log.
New support or feature requests created in an intake project are automatically labeled by type and routed to the right person — design requests go to the design team, bug reports go to engineering, all without a triage meeting every morning.
At the end of each sprint, any uncompleted tasks are automatically moved to the backlog with a "carried over" label. New sprint tasks are auto-assigned based on capacity rules. Sprint closing goes from a 30-minute manual cleanup to clicking "Start new sprint".
When a design task moves to "Ready for Review", the reviewer is automatically assigned and the #design-reviews channel is notified. When they approve it, status changes to "Approved" and the original requester is notified. No manual coordination needed.