---
metadata:
  - name: generator
    content: Diplodoc Platform v5.64.0
alternate:
  - https://yandex.ru/support/tracker/en/manager/create-queue-from-template.md
  - https://yandex.ru/support/tracker/ru/manager/create-queue-from-template.md
  - href: https://yandex.ru/support/tracker/en/manager/create-queue-from-template.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.ru/support/tracker/en/llms.txt?revision=r21825371
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt?revision=r21825371

# Creating a queue from a template

Choose this method if you want to quickly create a queue with ready-made settings. You can add test issues to the queue: they will help you understand what a queue is and how to work in it.

### Start creating a queue {#start}

1. In the left panel, select ![](../_assets/svg/queues-ni.svg) **Queues**, then click ![](../_assets/svg/add-icon.svg)</svg> at the top.
1. Select the ![](../_assets/svg/move-local-field.svg) **Create from template** option.

![](../_assets/queues/create-queue.png =600x){.border-blue}

### Select a template {#select}

Tracker recommends a template based on your company profile — if you need a different one, click **View all templates**.

Click a template to check its settings: which [statuses](*status) and [issue types](*issue-type) it includes, and whether it has additional features, such as [SLA rules](*sla) or a linked form for collecting requests.

Once you have decided on a template, click **Next**.

![](../_assets/quick-start/create-queue-step-1.png =800x){.border-blue}

### Come up with a name and key {#key}

<!-- source: en/_includes/create-queue.md -->
To create a queue, you need to come up with a key and a name. Try using the keys that reflect the purpose of the queue. For example, the `HR` key is suitable for issues in the Human Resources department, while `SUPPORT` is good for Support issues.

A queue key is a unique code that enables you to identify the queue. Each issue in the queue is assigned an issue key that consists of the queue key and a sequential number.

Queue keys must meet the following requirements:
- A key can only include Latin characters without spaces or special characters.
- The queue key must be unique: a new queue can't be assigned a key that was previously used by a deleted queue.
- The queue key must be allowed. There are several keys you can’t use for a queue, such as `ADMIN` or `SETTINGS`.
<!-- endsource: en/_includes/create-queue.md -->

### Configure queue access {#issues-examples}

If you are just starting out in Tracker, enable the ![](../_assets/svg/enable-switch.svg) **Add example issues** option. In test issues, you can change any parameters and see what changes. They will also help you see how issues with different statuses look on the board or on the Gantt chart.

![](../_assets/quick-start/create-queue-step-3.png =800x){.border-blue}


### Confirm queue creation {#confirm}

<!-- source: en/_includes/create-queue.md -->
Check the settings and click **Open queue**. The new queue will appear in the ![](../_assets/svg/queues-ni.svg) **Queues** section of the left panel.
<!-- endsource: en/_includes/create-queue.md -->

### How to edit a template {#edit-work-process}

Over time, you may notice that your workflow has stages that are not provided for in the template, such as `Тестирование` or `Ожидание ответа от юристов`.

You can always add new stages or create transition rules between existing ones: for example, you can prohibit closing an issue without going through the `Согласование` status. To do this, go to ![](../_assets/svg/settings.svg)</svg> **Queue settings** → **Workflows**. For details on how to configure everything, see the article [Adding a status to a workflow](https://yandex.ru/support/tracker/en/manager/workflow-status-edit.md#add-status).

![](../_assets/add-status.gif =750x){.border-yes}

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

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

[*status]: A status is an issue parameter that shows the current stage of the issue. For example ![](../_assets/svg/initial.svg), ![](../_assets/svg/progress.svg), ![](../_assets/svg/end.svg).

[*issue-type]: A type is an issue parameter that helps you categorize issues by their purpose. For example: **New Feature**, **Bug**, **Improvement**. You can set up different workflows for different types.

[*sla]: An SLA is a time frame within which an issue in a queue must be processed. If the time frame is exceeded, the timer owner receives a notification.