---
metadata:
  - name: generator
    content: Diplodoc Platform v5.54.2
  - property: og:type
    content: article
  - property: article:section
    content: Автоматизации
  - property: og:title
    content: Как задать условие срабатывания триггера
  - property: article:tag
    content: Сборник инструкций
alternate:
  - https://yandex.ru/support/tracker/en/user/set-condition.md
  - https://yandex.ru/support/tracker/ru/user/set-condition.md
  - href: en/user/set-condition.md
    type: text/markdown
    title: Markdown version
  - href: ../llms.txt
    type: text/markdown
    title: llms.txt
title: How to set an automation trigger condition in Yandex Tracker
description: From this article, you'll learn how to set an automation trigger condition in Yandex Tracker.
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt


# How to set a trigger condition

## Adding a condition {#section_set_condition}

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

1. In the ![](../_assets/svg/filter-icon-for-autoaction.svg) **Under condition** section, select a condition: an event related to updating an issue or adding a comment, or editing issue parameters.

   If you don't see the condition you need in the section, click **More conditions** ![](../_assets/svg/unwrap.svg)</svg> and select it from the list.

   <!-- source: en/_includes/automation-list-delay.md -->
   {% note tip "" %}

   To find a [local queue field](https://yandex.ru/support/tracker/en/local-fields.md), 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`).

   {% endnote %}
   <!-- endsource: en/_includes/automation-list-delay.md -->

1. Choose an event or [comparison operation](#comparison-operation) depending on the condition type.

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

   ![image](../_assets/boolean-ni.png =600x){.border-yes}

1. 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.

1. 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 ![](../_assets/svg/group-condition.svg)</svg>, and select **Convert to condition group**.

    * To group a condition with an existing one: select a condition, click ![](../_assets/svg/group-condition.svg)</svg> and then **Group it with**, and select a condition to group it with.


## Usage examples for conditions {#examples}

- Changing the **Assignee** field value: [Issue board](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#board)
- **Event** → **Issue changed**: [Automatically assign an issue assignee](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#assign_ticket)
- **Event** → **Formula fields changed**: [Automatically calculate the date difference](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#tracker_data)
- **Action with link** → **Link created**: [Change issue status after creating a link](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#new-link)
- **SLA limit violation**: [Change issue priority when an SLA timer expires](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#sla-excess)
- **Checklist**: [Change issue status after completing a checklist](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#checklist-done)
- **Comment text**: [Change issue status if a comment with specific text is added](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#comment)
- **Related issue parameters**: [Close a parent issue after closing all subtasks](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#sub-issues-done)

## Comparison operators {#comparison-operation}

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**
{width=33%} |  **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 to** → `8h`
> ||
> || 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 to** → `8h`
> ||
> || 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**

{% note info "" %}

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

{% endnote %}
||
|| 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 elements** → `Hello` 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.
||
|#

<!-- source: en/_assets/style/image.md -->

<!-- endsource: en/_assets/style/image.md -->