---
metadata:
  - name: generator
    content: Diplodoc Platform v5.64.0
alternate:
  - https://yandex.ru/support/tracker/en/manager/create-queue-from-nothing.md
  - https://yandex.ru/support/tracker/ru/manager/create-queue-from-nothing.md
  - href: https://yandex.ru/support/tracker/en/manager/create-queue-from-nothing.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 scratch

Choose this option if you are an experienced Tracker user and know which workflow your team needs.

### 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/icon-edit4.svg)</svg> **Create from scratch** option.

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

### Select the basic queue settings {#settings}

In the workflow designer, add statuses and issue types. Then select the issue views you are used to working with, such as a board or Gantt chart.

![](../_assets/queues/create-queue-from-zero.png =600x){.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 -->


### 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 -->

### Add rules for transitioning between statuses {#edit-work-process}

In a new queue, an issue can be moved to any status. You can restrict such transitions: for example, prevent closing an issue without going through the `Согласование` status. 

Go to ![](../_assets/svg/settings.svg)</svg> **Queue settings** → **Workflows**. For details on how to configure everything, see the article [Add a transition between statuses](https://yandex.ru/support/tracker/en/manager/workflow-action-edit.md#add-action).

![](../_assets/transition-on-diagram.gif =750x){.border-yes}

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

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