A rule consists of elements. The minimum two elements that need to be configured in a rule are a trigger and an action.

Think of the trigger as "WHEN something happens". The action is the counterpart of "THEN do something".

Basic rules do not need more elements! 


Triggers

Triggers define whether or not a rule should be executed. A trigger must be the first element when configuring a rule, and can only occur once per rule.

Triggers are generally based on field, issue, project or system events, but can also be scheduled to only execute at certain times.

Automation Toolbox provides the following triggers:





Selectors

Selectors provide the ability to search for specific issues within a rule and then take actions against those issues found.

When configuring a rule, you can add multiple selectors depending on the trigger type and the processing that should take place. Selectors can be added to triggers and conditions, but not to selectors themselves (which means they must not be nested).

Automation Toolbox provides the following selectors:


The options actually available depend on which other elements (triggers) have been selected upfront.



Conditions

Conditions provide the ability to further refine and control processing. You can configure complex Rules containing multiple and/or nested Conditions. Depending on the type of Trigger (or Selector) the following Condition options will be made available:

Conditions provide the ability to further refine and control processing. You can configure complex rules containing multiple and/or nested conditions.

Automation Toolbox provides the following conditions:


The options actually available depend on which other elements (triggers and/or selectors) have been selected upfront.



Actions

Actions determine the type of field, issue, transition, comment or email processing that should take place.

One or more actions can directly follow a trigger, any condition or any selector. You can add as many actions as needed.

Automation Toolbox provides the following actions:


The options actually available depend on which other elements (triggers and/or selectors) have been selected upfront.



Expression Parser

Automation Toolbox uses a powerful expression parser for interpreting expressions with logicalmathematical, date-time and string-text terms. This parser is a fundamental part of Automation Toolbox and is used by various features in the app.

If you are already familiar with how the parser works, you might want to have a look at Expression Parser 201 - All functions. This page contains a comprehensive overview of all functions that are currently available for the parser. 

Are you looking for a specific use case or function? Check out the subsections of the Expression Parser 201!





On this page

  • No labels