---
metadata:
- name: generator
content: Diplodoc Platform v5.47.3
alternate:
- https://yandex.com.tr/support/tracker/en/dev-process-automation.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt
# Automating recurring actions
You can automate common actions related to Tracker issues using [triggers, auto actions, and macros](https://yandex.com.tr/support/tracker/en/automation.md). You can update issue parameters based on events, either periodically or on a command, as well as create new issues by schedule.
Let's look at some examples of how you can automate certain actions in Tracker:
## Picking assignees automatically {#auto-assign-executor}
If a certain issue falls under the responsibility of a specific employee, you can automatically make them an assignee for that issue using [triggers](https://yandex.com.tr/support/tracker/en/user/create-trigger.md). When the conditions are met, the trigger automatically updates the issue parameters.
For example, the tester should start testing a new product feature once the developer changes the issue status to **Ready for testing**. To automatically make a test engineer an issue assignee, set up the trigger as follows:
1.
In the left-hand panel, click **Queues** and select a queue. {#queue}
1.
In the top right corner of the queue page, click **Queue settings**. {#settings}
1. In the left panel, select **Automation**.
1.
In the top right corner, click **Create** → **Trigger**. {#create-trigger}
1. Enter a name for the trigger.
1. Set the trigger to fire when the issue's **Status** changes:
- Trigger conditions: The issue status has changed to **Ready for testing**.
- If you want a new assignee to be picked after a status update, add the trigger condition: specify the tester in the **Assignee** field.
{.border-yes}
Let's take another example, when one developer focuses on the server part of your product, and another developer works on its client part. Whenever any new errors relating to the server or client part arise, you can automatically set the responsible developer as an assignee using components and triggers:
1. In your queue, [configure the components](https://yandex.com.tr/support/tracker/en/manager/components.md) that refer to the **Server** and **Client** sides of the product. When creating a new error, add a relevant component to it right away.
1. Set up a trigger for server part errors:
- Trigger conditions: the value in the **Components** field changed to **Server**.
- Trigger action: specify the server side developer name in the **Assignee** field.
{.border-yes}
1. Set up a similar trigger for errors in the client part:
- Trigger conditions: the value in the **Components** field changed to **Client**.
- Trigger action: specify the client side developer name in the **Assignee** field.
For an example of how to set up a trigger to fire when the component changes, see [Automatically assign an issue assignee](https://yandex.com.tr/support/tracker/en/manager/trigger-examples.md#assign_ticket).
## Reminding the assignee about the deadline {#auto-remind-deadline}
To make sure that your assignees adhere to deadlines, you can send them reminders using automatic actions. An automatic action triggers automatically and updates the parameters of issues that meet your criteria.
Say, for example, that you need to check all issues in your queue once a day. If the issue is still pending, and the date specified in the **Deadline** field occurs in less than three days, you should update the issue with a comment and invite the assignee. For this, set up the following automatic action:
- Auto action type: **Issue update**.
- Frequency: Once per day.
- Filter parameters: a query written using the [query language](https://yandex.com.tr/support/tracker/en/user/query-filter.md):
```
Resolution: empty() AND Deadline: <= today() + 3d
```
{.border-yes}
- Issue action: send a comment and invite the user specified in the **Assignee** field.
For detailed instructions on how to set up auto actions, see [Auto update example](https://yandex.com.tr/support/tracker/en/user/autoaction-example.md).
## Creating recurring issues {#auto-create-task}
If you need to create issues by a template from time to time, you can use actions for this. For example, every week you can create an issue for data backup.
For this, set up the following automatic action:
- Auto action type: **Issue creation**.
- Frequency: Once a week on Fridays.
You can set the start and end dates of the interval within which the issues will be created automatically. It's no such interval is set, the issues will be created indefinitely.
{.border-yes}
- Queue action: Create an issue. Fill in the fields of the automatic issue creation template.
For more information on how to set up recurring issues, see [Setting up issue creation](https://yandex.com.tr/support/tracker/en/user/ticket-schedule.md#setup).