---
metadata:
  - name: generator
    content: Diplodoc Platform v5.66.1
  - property: og:type
    content: article
  - property: article:section
    content: Getting started
  - property: og:title
    content: Create a queue and workflow
  - property: article:tag
    content: Instructions
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: https://yandex.ru/support/tracker/en/quick-start/setup-for-team/create-queue.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.ru/support/tracker/en/llms.txt?revision=r22077802
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt?revision=r22077802


# 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, `Разработка сайта` or `Поддержка клиентов`. This will make it easier for you and your colleagues to find it, especially when there are many queues.

In addition to the name, each queue has a key — a unique code made up of Latin letters. It is included in links to queue issues and is required for some settings and API requests. You cannot change the key after creating a queue.

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

<!-- source: en/manager/create-queue-from-template.md -->
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}
<!-- endsource: en/manager/create-queue-from-template.md -->

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

<!-- source: en/manager/create-queue-from-template.md -->
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 -->
<!-- endsource: en/manager/create-queue-from-template.md -->

<!-- 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.