---
metadata:
  - name: generator
    content: Diplodoc Platform v5.47.3
alternate:
  - https://yandex.com.tr/support/tracker/en/quick-start/setup-for-team/create-automations.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt

# Automate frequent actions

{% note info "" %}

If your team is just starting to work in Tracker, don't rush into automations. First, identify which actions are time-consuming and automate those specifically.

{% endnote %}

When the process is well-established and the team is accustomed to Tracker, repetitive actions become noticeable: assigning the same assignees, sending reminders, leaving standard comments, and handling recurring issues start to consume time.

Automations help shift this routine onto Tracker. It can remind you about deadlines on its own, create issues on a schedule, and change issue parameters according to your rules. There are three tools for this:
-   **Trigger** changes an issue as soon as a specific event occurs in it.
-   **Auto action** runs on a schedule and can either create a new issue or modify an existing one.
-   **Macro** is an action that a user starts by clicking a button on the issue page.

## When to use a trigger {#trigger}

A trigger changes an issue as soon as a specific event occurs in it. For example, when an issue is set to the **Bug** type, developer Igor will be assigned as the assignee.

Start with one or two of the most common scenarios and add new ones as needed.

For more information, see [How do I set up a trigger?](https://yandex.com.tr/support/tracker/en/user/create-trigger.md).

## When to use an auto action {#automation}

An auto action is triggered on a schedule and runs for issues that meet a certain condition. For example, every day the assignee will receive reminders about issues where the deadline is less than a week away.

Auto actions are useful when you want to catch situations not tied to a specific human action: forgotten issues, missed deadlines, unfilled fields.

For more information, see [How to automate issue updates](https://yandex.com.tr/support/tracker/en/user/create-autoaction.md).

## When to use a macro {#macro}

A macro is an action that a user starts by clicking a button on the issue page.

Suppose a manager often repeats this sequence:
1.  Changes the issue status to **Canceled**.
1.  Removes the assignee.
1.  Leaves a standard comment.

These actions can be combined into a single macro and performed faster.

For more information, see [Setting up macros in Tracker](https://yandex.com.tr/support/tracker/en/manager/create-macroses.md).

## How to create a trigger, auto action, or macro {#create}

You need to configure automations separately for each queue.

1.  Open the queue and at the top, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon nv-aside-header-footer-item__icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none"><path fill="currentColor" fill-opacity=".85" fill-rule="evenodd" d="M8.875 2.125h2.25a.5.5 0 0 1 .5.5v.23c0 1.925 2.083 3.128 3.75 2.165l.2-.115a.5.5 0 0 1 .682.183l1.125 1.949a.5.5 0 0 1-.183.683l-.2.115c-1.666.962-1.666 3.368 0 4.33l.2.115a.5.5 0 0 1 .183.683l-1.125 1.949a.5.5 0 0 1-.683.183l-.199-.115c-1.667-.963-3.75.24-3.75 2.165v.23a.5.5 0 0 1-.5.5h-2.25a.5.5 0 0 1-.5-.5v-.23c0-1.925-2.083-3.128-3.75-2.165l-.2.115a.5.5 0 0 1-.683-.183l-1.125-1.949a.5.5 0 0 1 .183-.683l.2-.115c1.667-.962 1.667-3.368 0-4.33l-.2-.115a.5.5 0 0 1-.183-.683l1.125-1.949a.5.5 0 0 1 .683-.183l.2.115c1.667.963 3.75-.24 3.75-2.165v-.23a.5.5 0 0 1 .5-.5zm-2 .5a2 2 0 0 1 2-2h2.25a2 2 0 0 1 2 2v.23a1 1 0 0 0 1.5.866l.2-.115a2 2 0 0 1 2.731.732l1.125 1.949a2 2 0 0 1-.732 2.732l-.2.115a1 1 0 0 0 0 1.732l.2.115a2 2 0 0 1 .732 2.732l-1.125 1.949a2 2 0 0 1-2.732.732l-.199-.115a1 1 0 0 0-1.5.866v.23a2 2 0 0 1-2 2h-2.25a2 2 0 0 1-2-2v-.23a1 1 0 0 0-1.5-.866l-.2.115a2 2 0 0 1-2.732-.732l-1.125-1.949a2 2 0 0 1 .732-2.732l.2-.115a1 1 0 0 0 0-1.732l-.2-.115a2 2 0 0 1-.732-2.732l1.125-1.949a2 2 0 0 1 2.732-.732l.2.115a1 1 0 0 0 1.5-.866v-.23zM12.25 10a2.25 2.25 0 1 1-4.5 0 2.25 2.25 0 0 1 4.5 0zm1.5 0a3.75 3.75 0 1 1-7.5 0 3.75 3.75 0 0 1 7.5 0z" clip-rule="evenodd"/></svg></svg> **Queue settings**.
1.  Go to the **Automations** tab and click **Create** <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" class="g-icon" fill="currentColor" stroke="none" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 16 16"><path fill="currentColor" fill-rule="evenodd" d="M2.97 5.47a.75.75 0 0 1 1.06 0L8 9.44l3.97-3.97a.75.75 0 1 1 1.06 1.06l-4.5 4.5a.75.75 0 0 1-1.06 0l-4.5-4.5a.75.75 0 0 1 0-1.06Z" clip-rule="evenodd"/></svg></svg>.

![](../../_assets/quick-start/create-automation.png =850x){.border-blue}
*Section in queue settings*

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

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