Automations

Automations are rules Hilbana runs on its own over issues when an event happens: «when this happens, if these conditions hold, then do this».

What it is

Managed in Settings → Automations. Each rule can be enabled, disabled, edited and deleted, and comes with a natural-language preview of what it does.

Triggers, conditions and actions

• When (trigger): issue created, or a change of state, assignee, priority, project, cycle or milestone.
• If (conditions, optional and combined): the target value is in a list, the issue is in certain projects, or it has one of certain labels.
• Then (actions, in order): change state, assign, add or remove a label, comment, or trigger an outgoing webhook.

Details worth knowing

• Automations are a paid-plan feature (see Billing); only admins see the editor.
• They run on the server, after the event is recorded. One automation doesn’t trigger another (no loops), and if a rule fails it doesn’t affect the rest or revert the issue’s change.
• The change-state action only accepts states from the same team as the issue.
• A comment created by a rule is signed by the system, not by the person who triggered the event.

Related: Issues · Workflow states · Outgoing webhooks · Agents.