---
metadata:
  - name: generator
    content: Diplodoc Platform v5.54.5
  - 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/create-autoaction.md
  - https://yandex.ru/support/tracker/ru/user/create-autoaction.md
  - href: en/user/create-autoaction.md
    type: text/markdown
    title: Markdown version
  - href: ../llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt


# How to automate issue updates

With auto actions, you can automatically update issues based on the conditions you set in filters. Issues will be updated as scheduled. For example, you can invite a lead to comment if the issue hasn't been updated for a long time.

{% note warning "" %}

<!-- source: en/_includes/autoaction-100.md -->
When triggered, the auto action processes only the first 100 issues that meet the specified criteria. Other issues will be processed the next time the auto action is triggered. {#100issues}
<!-- endsource: en/_includes/autoaction-100.md -->


{% endnote %}

<!-- source: en/_includes/autoaction-100.md -->
To set up auto actions, the [**Queue management** access rights](https://yandex.ru/support/tracker/en/manager/queue-access.md) are required. You can add up to 100 auto actions to one queue. {#access}
<!-- endsource: en/_includes/autoaction-100.md -->

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click ![](../_assets/svg/queues-ni.svg) **Queues** and select a queue. {#queue}

   In the top right corner of the queue page, click ![](../_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/transition-page.md -->
   In the top right corner of the queue page, click ![](../_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. Select **Automation** in the left-hand panel.

1. In the top right corner, click **Create** → **Auto action**.

1. Select **Issue update** as the type of auto action.

1. Set the name for the auto action.
    You can add a description below the name.

1. Set the ![](../_assets/svg/alarm-clock-icon.svg) **Trigger schedule**, which is the interval of automatic issue update in hours or days.
    To track issue updates, enable the **Send a notification every time the trigger fires** option.

1. Select the issues to apply the auto action to:
    - To have the auto action triggered for issues whose parameters match specific values, select the **When the issue meets the condition** mode. You can add multiple conditions. The auto action will trigger if all the conditions hold at the same time.
    - To have the auto action triggered for issues that meet the filter criteria, select the **When the issue matches the QL query** mode and set the conditions in the line using the [query language](https://yandex.ru/support/tracker/en/user/query-filter.md).

1. Under ![](../_assets/svg/arrow-icon-for-autoaction.svg) **Perform actions**, [set one or more actions on the issue](#set-autoaction).

1. To save an auto action, click **Create auto action**.

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

The new automation will appear in the list in a few seconds after being added.

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

## Configuring actions {#set-autoaction}

Under ![](../_assets/svg/arrow-icon-for-autoaction.svg) **Perform actions**, set up one or more actions:

- ![](../_assets/svg/check-in-round.svg)</svg> [**Change issue status**](#change-status)
- ![](../_assets/svg/icon-card.svg)</svg> [**Change field value**](#change-field-value)
- ![](../_assets/svg/comment.svg)</svg> [**Add comment to issue**](#create-comment)
- ![](../_assets/svg/value.svg)</svg> [**Calculate value**](#calculate-value)
- ![](../_assets/svg/query-language.svg)</svg> [**HTTP request**](#create-http)

### Changing issue status {#change-status}

Set a new issue status. The available statuses are determined by the [workflow](https://yandex.ru/support/tracker/en/manager/workflow-status-edit.md) settings.

{% note warning "" %}

The auto action is run by a [Robot](*robot) `yndx-tracker-cnt-robot@`. For the robot to change the issue status:

- If there are [conditions configured](https://yandex.ru/support/tracker/en/manager/workflow-action-edit.md#conditions) for the transition to the status that restrict user permissions for changing the status, add the robot `yndx-tracker-cnt-robot@` to the list of users.

- If a [transition screen is configured](https://yandex.ru/support/tracker/en/manager/workflow-action-edit.md#set-transition) for the transition to the status, make sure it doesn't have any required fields.

{% endnote %}

### Updating fields {#change-field-value}

<!-- source: en/user/set-action.md -->
Set one or multiple issue parameters:

1. Click ![](../_assets/svg/add-icon.svg)</svg> **Add parameter** and select an issue parameter.

    <!-- 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. Select an action:

    | **Action** | **Description** |
    ----- | -----
    | **Set value** | Specify the parameter value. |
    | **Clear field** | Delete a parameter value. |
    | **Add to list** | Add another parameter value (for parameters with multiple values). |
    | **Remove from list** | Remove a parameter value (for parameters with multiple values). |

1. Set a new value for the parameter.

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

You can't change the value of the **Parent ticket** field using an auto action.

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

### Adding comments to issues {#create-comment}

<!-- source: en/user/set-action.md -->
Write the comment text that will be added to an issue.

You can insert [values of issue fields](https://yandex.ru/support/tracker/en/user/vars.md) into the comment text. To do this, click ![](../_assets/console-icons/issues.svg)</svg> **Variables** and select one or more values. The comment field will show a sequence like `not_var{{issue.<field_key>}}`.

The comment is sent on behalf of the user who activates the trigger. If you want a robot to appear as the comment author, enable the **Send as robot** option.
<!-- endsource: en/user/set-action.md -->


### Calculating a value {#calculate-value}

<!-- source: en/user/set-action.md -->
You can set up a special field whose values are calculated automatically based on values entered in other fields.

To calculate the field value automatically:

1. Set a formula for calculating the value:
    - Click ![](../_assets/console-icons/issues.svg)</svg> **Add variable** and add a field formula with numeric values. The formula will include a [sequence](https://yandex.ru/support/tracker/en/user/vars.md) like `not_var{{issue.<field_key>}}`.
      If the required field is missing in Yandex Tracker, you can [create it](https://yandex.ru/support/tracker/en/user/create-param.md).
    - You can use mathematical symbols for addition `+`, subtraction `-`, multiplication `*`, and division `/`.
    - To set the priority of operations, use parentheses.
    - To calculate values for date fields, you can use expressions with the `today()` function. For example, the `today()+3d` function returns the date that is three days from now.

1. Click **Select a field** and set the field you want to put the calculated value into.

    {% note info "" %}

    If the field supports only integer values, the value will be rounded.

    {% endnote %}

For an example of implementing the function, see [Add the current date to a field](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#today).
<!-- endsource: en/user/set-action.md -->

### HTTP request {#create-http}

<!-- source: en/user/set-action.md -->
You can use HTTP requests to access the API of other services and set up integrations with them.


To send an HTTP request whenever the automation is triggered:

1. Select the HTTP request method.

1. Specify the [full URL of the resource](https://tools.ietf.org/html/rfc3986) to which the request will be sent. For example: `http://example.org/newfolder/newfile`.


1. Choose the authorization method:
    - **NoAuth**: No authorization.
    - [**Basic**](https://tools.ietf.org/html/rfc2617): You are prompted to enter your username and password.
    - [**OAuth 2.0**](https://tools.ietf.org/html/rfc6749): You are prompted to enter a token, authorization header, and token type.

1. When selecting the **Basic** or **OAuth 2.0** authorization type, enter authorization data.


   The authorization data (username, password, token, authorization header, token type) are transmitted in relevant fields and don't require to be re-entered in headers.

1. Enter the request body.

   You can add [issue field values](https://yandex.ru/support/tracker/en/user/vars.md) or custom variables to the request body. To do this, click ![](../_assets/console-icons/issues.svg)</svg> to the right of the field and choose the name for the field or value. The request body will include the `{{<variable_name>}}` sequence.

   {% note info "" %}

   You can also use variables in the resource URL and header value.

   {% endnote %}

1. Enter the headers and their values.

1. Add new variables if you need them in the request body or headers. For example, you can add an authentication key or other secret information.


   {% note info "" %}

   When you save the trigger, the variable's value is hidden, and you can't look it up later.

   {% endnote %}

When the automation is triggered, Tracker sends an HTTP request. The response can be any [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes).

If no response is received within 10 seconds, or if the response contains code 500, the request will be resent. Each request will be retried up to 5 times, with the delay between attempts increasing exponentially from 10 seconds.

#### Sample HTTP request settings {#http-examples}

- [Sending notifications from Yandex Tracker to messengers](https://yandex.ru/support/tracker/en/messenger.md)

- [Creating and updating a checklist in an issue](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#checklist)

- [Creating an issue with field values from its parent issue](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#create-ticket-with-params)

- [Updating an issue status, priority, and adding a comment in related issues](https://yandex.ru/support/tracker/en/manager/trigger-examples.md#update-related-tasks)
<!-- endsource: en/user/set-action.md -->

## Viewing the history of triggered auto actions {#autoaction-history}

To see when an auto action was triggered and its outcome, hover over it in the list of automations and click ![](../_assets/svg/actions.svg)</svg> → ![](../_assets/svg/history.svg)</svg> **History of triggers**.

You'll see the list of triggered auto actions in the right panel. For each run, you'll find this information:
 * Start time.
 * The number of issues handled and the total number of issues that meet the condition triggering the auto action.

   To view handled issues, click the line with the run info.

 * Issue handling progress (if it's not completed) or result.

[*robot]: A robot is a service account that Tracker uses to perform automated actions in issues.

[*token]: A token is a secret key for accessing the API. It authenticates the user or application, so it must not be shared with others.