Automation: when something changes, the next thing happens.
Trigger-based rules across your projects. Custom statuses, transition rules, validators and post-functions — so the repetitive parts of your workflow run themselves.
Automation, feature by feature.
Trigger → action rules
When an issue changes, fire the next step automatically — assign, transition, notify.
Custom statuses
Model your real workflow, not a generic To-Do / Doing / Done.
Transition rules
Control who can move work where, and under what conditions.
Validators
Block invalid transitions — require a field, an assignee, or an estimate first.
Post-functions
Run side effects on transition: set a field, add a comment, ping a channel.
Cross-project
Rules can span projects so org-wide policies stay consistent.
Encode the busywork once.
Every team has rituals: when a bug is closed, assign the reporter to verify; when an epic is done, notify the lead. Automation turns those rituals into rules that run without anyone remembering to.
Validators and post-functions make transitions trustworthy — you cannot move a card into Done without the fields that Done requires, and the right side effects always fire.
- Custom statuses, transitions, validators and post-functions.
- Trigger-based rules that span projects.
- Side effects on transition: fields, comments, notifications.
Automation questions
What can a rule do?
Transition issues, assign people, set fields, add comments and send notifications when a trigger condition is met.
Can I enforce required fields?
Yes. Validators block a transition until its conditions — required fields, assignee, estimate — are satisfied.
Do rules work across projects?
Yes, rules can be scoped to a project or applied across projects for org-wide consistency.
Get Automation — free.
It is included from your first workspace. Create one in seconds, no card required.