Automations

Automations are a project-level rule engine built into Stellary. Each rule follows a simple pattern: when something happens (trigger), if certain criteria are met (conditions), then perform an action.

Rules run server-side the instant an event occurs, so your workflow stays consistent whether your team interacts from the board, the list view, or the API. Every execution is logged, giving you a complete audit trail for compliance and debugging.

Open your project settings and navigate to the Automations tab. Click "New Rule" to start the creation wizard. Each rule consists of three parts:

• Trigger — the event that starts the rule (e.g., a card is moved)
• Conditions — optional JSON-based filters that narrow when the rule fires (e.g., only for cards with a specific label or priority)
• Action — what Stellary does when the trigger and conditions match (e.g., change the card status)

Give your rule a descriptive name, configure the three parts, and save. The rule is active by default and will start firing immediately.

Stellary supports seven trigger types that cover the most common project events. Pick the one that matches the moment you want to react to:

Conditions let you fine-tune when a rule should fire. They use a JSON-based filtering syntax that can match against any card property — column, priority, assignee, labels, custom fields, and more.

You can combine multiple conditions, and all must be true for the action to execute. Examples:

• Column filter— fire only when the target column is "Done"
• Priority filter — fire only for High or Medium priority cards
• Label filter— fire only when the card has the "Bug" label
• Assignee filter — fire only when the card is assigned to a specific team member

Conditions are optional. If you leave them empty, the rule fires for every occurrence of the trigger.

The action defines what happens when the trigger fires and all conditions are met. Stellary provides several action types:

• Move card — automatically move a card to a specific column
• Change status — set the card status (open, in progress, done, cancelled)
• Assign member — assign the card to a specific team member
• Update priority — set the card priority level
• Archive card — hide the card from active views once the workflow is complete

Each action runs server-side. If an action cannot apply (for example because the target column no longer exists), that run is skipped without blocking other automation rules.

Here are four real-world automations to get you started. Each one combines a trigger, an optional condition, and an action to eliminate manual work:

The Automations tab shows configured rules, whether they are active, and a trigger → action summary. Technical execution details are logged server-side for diagnostics.

• Status — enable or pause a rule without deleting it
• Summary — verify the configured trigger, conditions, and action
• Diagnostics — backend logs capture action errors

Use this tracking to quickly confirm what should happen, then update the rule if the target column, member, or status has changed.

Each rule has a toggle to enable or disable it individually. Disabling a rule pauses it immediately — no triggers will be evaluated and no actions will fire until you re-enable it.

This is useful when you need to:

• Temporarily pause a rule during a migration or bulk import without deleting it
• Debug an unexpected behavior by isolating rules one at a time
• Prepare rules in advance — create them in a disabled state and activate them when your team is ready

Disabled rules are clearly marked in the Automations list, and their execution traces are preserved so you never lose historical data.