Setting trigger conditions

Adding a condition

To specify issue updates that will fire the trigger, set a condition:

  1. In the  Under condition section, select a condition: an event of updating an issue, adding a comment, or editing issue parameters.

    If you don't see the condition you need in the section, click All conditions  and select it from the list.

    To find a local queue field, enter the key of the queue where you want to set up an automation and a period before the field name (for example, DEVS.Tester).

  2. Choose an event or comparison operation depending on the condition type.

    If a comparison operation is selected, specify the value to be compared.

    image

  3. If you want the trigger to fire when multiple conditions are met, click Add condition and select the required option from the list.

    By default, a trigger fires when all conditions are met at once: the logical AND applies to the condition group. If you want the trigger to fire when at least one condition is met, click the operator icon to the left of the condition group. As a result, the logical OR will be selected.

  4. You can add a number of nested groups of conditions that will match the logical AND or logical OR:

    • To create a group or add a new condition to an existing one, select a condition, click , and select Convert to condition group.

    • To group a condition with an existing one: select a condition, click and then Group it with, and select a condition to group it with.

Usage examples for conditions

Comparison operators

If the trigger's condition includes a comparison operation, the condition will be checked each time the issue changes. If the condition is met, the trigger fires.

Different comparison operations are available for different parameter types.

You can specify additional options for certain comparison operations:

  • Parameter changed: The trigger fires when the parameter value changes and a condition is met as a result.
  • Ignore case: Treat uppercase characters as equivalent to the same lowercase characters.
  • Ignore markup: Ignore the Markdown markup in the text.

The comparison operators listed below are supported.

Comparison operations

Description

Is equal to

A condition is met when the issue parameter value matches the specified value.

For example, if you want the trigger to fire when an assignee is set for an issue with the Open status, you can use the condition:

Status → is equal to → Open
AND
Assignee → field value set

Became equal to

A condition is met if the issue parameter value changes and a new value matches the specified one.

For example, if you want the trigger to fire when an issue's status changes to In progress , you may use the condition:

Status → Became equal to → In progress

Greater than, greater than or equal to, less than, less than or equal to

Comparison operations for parameters with numerical values.

For example, if you want the trigger to fire each time the issue is changed and the Time spent field value exceeds eight hours, you may use the condition:

Time spent → is greater than or equal to8h

Became greater than, became greater than or equal to, became less than, became less than or equal to

A condition is met when the issue parameter value changes and the comparison is true for a new value.

For example, if you want the trigger to fire when more than eight hours have been spent on the issue, you may use the condition:

Time spent → Became greater than or equal to8h

Later than date, later or equals date, before date, before or equals date

Comparison operations for date parameters.

Field value is empty, field value is not empty

Operations check whether the field is filled in.

Field value set, field value changed, or field value deleted

Operations check whether a parameter value was added, updated, or deleted.

For example, if you want the trigger to fire when an assignee is set for an issue, you may use the condition:

Assignee → Field value set

The trigger will also fire if the parameter value is set when creating an issue (for example, if the assignee is specified).

Elements quantity is equal, elements quantity is greater, elements quantity is less

Comparison operations for fields that may contain multiple elements, such as Tags.

Contains none of items, contains all items, contains any of items

Comparison operations for fields that may contain multiple elements, such as Tags.

For example, if you want the trigger to fire when the hello tag is added to an issue, you may use the condition:

Tags → contains all elementsHello with the option Parameter changed

Contains none of given strings, does not contain substring, matches string, contains any from given strings, contains substring

Comparison operations for the Comment text condition, which check for the specified text in the comments.