---
metadata:
  - name: generator
    content: Diplodoc Platform v5.54.2
  - property: og:type
    content: article
  - property: article:section
    content: С чего начать
  - property: og:title
    content: Создать очередь и рабочий процесс
  - property: article:tag
    content: Сборник инструкций
alternate:
  - https://yandex.ru/support/tracker/en/quick-start/setup-for-team/create-queue.md
  - https://yandex.ru/support/tracker/ru/quick-start/setup-for-team/create-queue.md
  - href: en/quick-start/setup-for-team/create-queue.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


# Create a queue and workflow

{% note info "" %}

Tracker already has your first queue ready: you can create issues for your team in it. [Create your first issue](https://yandex.ru/support/tracker/en/quick-start/setup-for-team/create-issue.md)

If one queue is not enough and you want to separate workflows, follow the instructions in this article.

{% endnote %}

![](../../_assets/quick-start/first-queue.png =850x){.border-blue}
_Your first queue_

## What is a queue {#about-queue}


A queue is a space where issues are stored. For example, you can use a queue for a project, product, or line of work.

A workflow in a queue consists of the stages of working on an issue from creation to completion. The process is sometimes also called the issue lifecycle.


## Step 1. Select a queue template {#step-1}

In the left panel, click ![](../../_assets/svg/queues-ni.svg) **Queues** → **Create queue**. Tracker will prompt you to select a queue template—this is a preset with all the basic settings. When choosing, base your decision on what your team does.

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

## Step 2. Name the queue {#step-2}

Give the queue a clear name—for example, "Website Development" or "Customer Support". This will make it easier for you and your colleagues to find it, especially when you have many queues.

Besides a name, each queue has a key—a unique code consisting of Latin letters. The key is part of the link to the queue and its issues; you need to specify it in API requests and in auto action settings.

You cannot change the key after creating the queue.

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

## Step 3. Configure queue access {#step-3}

Define who can view the issues. If the issues will contain sensitive data that only one team should see, select the option ![](../../_assets/svg/transition-conditions.svg)</svg> **Me and issue participants**.

You can change or refine the access settings later: open the queue and at the top click ![](../../_assets/svg/settings.svg)</svg> **Queue settings** → **Permissions**. For more information, see the article [How to configure access rights in a queue](https://yandex.ru/support/tracker/en/manager/queue-access.md).

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

## Add your own settings to the template {#add-process}

Over time, you might notice that your work includes stages not provided for in the template, for example, "Testing" or "Awaiting response from legal".

You can always add new stages or simply adjust the names and transitions between existing stages. To do this, go to ![](../../_assets/svg/settings.svg)</svg> **Queue settings** → **Workflows**. For detailed instructions on how to configure everything, see the article [Issue statuses](https://yandex.ru/support/tracker/en/manager/workflow-status-edit.md).

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

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

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