Automations
Automations let you define Trigger → Conditions → Actions rules that execute tasks automatically when events occur in the project, reducing repetitive manual work.
Access in Project Settings → Automations.
Rule Structure
When [TRIGGER] occurs
And [CONDITIONS] are true (optional)
Then [ACTIONS] are executed
Each rule has:
- Name — rule identifier
- Active / Inactive — toggle to enable or disable without deleting
- One trigger — the event that fires the rule
- Zero or more conditions — optional filters applied to the issue
- One or more actions — what happens when the rule fires
Available Triggers
| Trigger | When it fires |
|---|---|
issue.created |
A new issue is created in the project |
issue.updated |
Issue fields are updated (excluding status) |
status.changed |
An issue's status changes |
Available Conditions
Conditions are optional and evaluated with AND logic — all must be true for the action to run.
| Field | Available operators | Example values |
|---|---|---|
priority |
equals, not_equals, contains |
CRITICAL, HIGH, MEDIUM, LOW, TRIVIAL |
type |
equals, not_equals, contains |
EPIC, STORY, TASK, BUG, SUBTASK, IMPROVEMENT, HOTFIX, SPIKE, RESEARCH, TECHNICAL_DEBT |
status |
equals, not_equals, contains |
Exact name of the status configured in the project |
Available Actions
| Action | Description |
|---|---|
send_email |
Send an email to configured recipients |
set_status |
Move the issue to a specific status |
assign_user |
Assign the issue to a project member |
Details: Send Email (send_email)
Configure subject, email body, and recipients:
| Recipient type | Description |
|---|---|
REPORTER |
Who created the issue |
ASSIGNEE |
The issue's assignee(s) |
PROJECT_ADMINS |
All members with the PROJECT_ADMIN role |
ORG_OWNER |
Member(s) with the OWNER role in the organization |
CUSTOM |
A specific email address entered manually |
Custom SMTP per rule:
Each send_email action can use its own SMTP server, independent of the platform's global SMTP:
| Field | Description |
|---|---|
| Host | SMTP server address (e.g. smtp.gmail.com) |
| Port | 587 for STARTTLS · 465 for direct SSL/TLS |
| User | SMTP login or email |
| Password | SMTP password |
Note on ports: use
465for SSL/TLS and587for STARTTLS. An incorrect port will cause a connection timeout.
If no custom SMTP is configured, the platform's global SMTP is used.
Rule Examples
Notify admins when status changes
Trigger: status.changed
Condition: status equals "In Review"
Action: send_email → PROJECT_ADMINS
Subject: Issue in review
Assign a member to critical bugs
Trigger: issue.created
Condition: type equals BUG AND priority equals CRITICAL
Action: assign_user → [selected user]
Auto-move hotfix to in progress
Trigger: issue.created
Condition: type equals HOTFIX
Action: set_status → "In Progress"
Execution Order
When multiple rules are triggered by the same event, they execute in creation order.
Automations run asynchronously, after the transaction that generated the event commits — ensuring the issue is fully saved before any processing occurs.
Monitoring
Each rule displays an execution counter in the automations list. Execution errors (e.g. email send failure due to incorrect SMTP) are recorded in server logs.