The core concept in Automation is the rule. A rule describes what to do in response to an event.
Automation rules are made up of three parts:
Collectively these are called components.
A rule describes what to do in response to a triggering event. Rules can be as simple as a single action, or include complex conditions and branching.
Rules are identified by an id.
Every rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Atlassian products, such as when an issue or page is created or when a field value is changed. You can also trigger rules to run from third party services like Bitbucket or GitHub.
There are also "manual" triggers that allow users to trigger rules from various UI locations throughout Atlassian products.
View the list of available triggers.
Conditions allow you to narrow the scope of your rule. They must be met for your rule to continue running. For example, you can set up your rule to only escalate an issue if it is high priority.
If a condition fails, the rule will stop running and no actions following the condition will be performed.
View the list of available conditions.
Actions are the doers of your rule. They allow you to perform tasks within a site or in an external product.
View the list of available actions.
Branching allows a rule to act on multiple objects, or to act on objects other than what triggered the rule.
Branching "forks" the rule execution and puts the new object in context so it can be acted on.
Rate this page: