--- metadata: - name: generator content: Diplodoc Platform v5.63.0 - property: og:type content: article - property: article:section content: Configure the queue - property: og:title content: How to create a queue - property: article:tag content: Instructions alternate: - https://www.yandex.ru/support/tracker/en/manager/create-queue.md - https://www.yandex.ru/support/tracker/ru/manager/create-queue.md - href: https://www.yandex.ru/support/tracker/en/manager/create-queue.md type: text/markdown title: Markdown version - href: https://www.yandex.ru/support/tracker/en/llms.txt rel: describedby --- > **Documentation Index:** Fetch the complete configuration index at https://www.yandex.ru/support/tracker/en/llms.txt # How to create a queue Each issue belongs to a queue. Queues are usually created for issues that belong to the same subject. These can be issues of a project, department, or team. There are three ways to create a queue in Yandex Tracker: - [By using a template](#create-from-template) - [From scratch](#create-manual). - [Copy another queue](#create-from-copy). A Yandex Tracker administrator can [restrict the ability to create queues](https://www.yandex.ru/support/tracker/en/manager/queue-access.md#queues). If you can't create a queue, contact an administrator. {% note warning "" %} The queue owner is the user who created it. The owner can configure the queue themselves or grant other users [permission to change queue parameters](https://www.yandex.ru/support/tracker/en/manager/queue-access.md#set-access). {% endnote %} ### Enter a key for the queue {#key} 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`. The queue key can be used: - For searching issues — specify the queue key in [filter conditions](https://www.yandex.ru/support/tracker/en/user/create-filter.md) and in the [query language](https://www.yandex.ru/support/tracker/en/user/query-filter.md). - For direct access to the queue via the address: `(https://tracker.yandex.com/queue_key)`. ## Creating a queue using a template {#create-from-template} 1. On the left panel, click ![](../_assets/svg/queues-ni.svg) **Queues** → **Create queue**. {#create-web} ![](../_assets/queues/create-queue-methods.png){.border-yes} 1. Select the appropriate queue template. For more information about templates and their settings, see [Queue templates](https://www.yandex.ru/support/tracker/en/manager/work-process.md). {#template} 1. Enter a name and key for the new queue. {#name-and-key} 1. Specify who can view issues in this queue: * **All employees**: The queue issues will be available to all organization employees. * **Me and issue participants**: The queue issues will only be available to the queue owner and the users specified in the **Author**, **Assignee**, **Followers**, and **Access** fields. 1. Click **Next**. The new queue appears in the ![](../_assets/svg/queues-ni.svg) **Queues** section on the left panel. {#created-web} ## Manually creating and setting up a queue {#create-manual} If none of the preset queue types fit your issues, you can configure all the settings for the new queue manually: {#manual} 1. On the left panel, click ![](../_assets/svg/queues-ni.svg) **Queues** → **Create queue**. {#create-web} 1. Select ![](../_assets/svg/icon-edit4.svg) **From scratch**. {#from-zero} 1. Enter a name and key for the new queue. {#name-and-key} 1. Specify who can view issues in this queue: * **All employees**: The queue issues will be available to all organization employees. * **Me and issue participants**: The queue issues will only be available to the queue owner and the users specified in the **Author**, **Assignee**, **Followers**, and **Access** fields. 1. Choose the queue workflow, which defines the issue statuses and the rules for moving between them. For more information, see [Workflows: how to set up statuses, transitions, and issue types in a queue](https://www.yandex.ru/support/tracker/en/manager/workflow.md) {#workflow} 1. Select the issue types to be used in the queue and specify the default type. {#issue-types} 1. Click **Next**. The new queue appears in the ![](../_assets/svg/queues-ni.svg) **Queues** section on the left panel. {#created-web} ## Copying a queue {#create-from-copy} If you want to use the settings of an existing queue, copy the queue: {#copy-queue} 1. On the left panel, click ![](../_assets/svg/queues-ni.svg) **Queues** → **Create queue**. {#create-web} 1. Select ![](../_assets/svg/copy-template.svg) **Copy another queue**. {#copy} 1. Enter the key or name of the queue whose settings will be copied. {#source} 1. Enter a name and key for the new queue. {#name-and-key} 1. Click **Next**. The new queue appears in the ![](../_assets/svg/queues-ni.svg) **Queues** section on the left panel. {#created-web} Not all settings of the original queue are copied. #| || **Copied** | **Not copied** || || Workflows | Macros || || Issue types | Triggers || || Access settings | Auto actions || || Queue description | Integrations || || Notification settings | SLA rules || || Default issue priority | Work schedules || || Required fields in issues | Time tracking || || Resolutions | Local fields in issues || |# #### Learn more: - [Workflows: how to set up statuses, transitions, and issue types in a queue](https://www.yandex.ru/support/tracker/en/manager/workflow.md)