Triggers define when a rule should be executed - so every rule starts with a trigger.

A trigger must be the first element when configuring a rule and can only occur once per ruleTriggers will generally listen to events. Typical events are field, issue, project, or system events (e.g. "A field was updated", "A new version was created").

Apart from events, a trigger can be:

Available automation triggers

The following triggers are available:

A trigger must be the first element in the rule configuration and can only occur once per rule.

For the rule to execute, the conditions configured for a chosen trigger must be met.


If you still have questions, feel free to refer to our support team.