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

# Copy queue

Choose this method if Tracker already has a queue with suitable settings and you don't want to configure everything from scratch.

{% cut "View the settings that will be copied" %}

#|
|| **Will be copied** | **Will not be copied** ||
|| 
- Settings from the **Workflows** section: transition rules between [statuses](*status) for different [issue types](*issue-type), available [resolutions](*resolution).
- Settings from the **Basic** section, such as the description and default priority of issues.
- Users from the **Permissions** and **Queue team** sections.
|
- Settings from the **Automations** section: macros, triggers, auto actions.
- Settings from the **Integrations** section, such as connected forms and mailboxes.
- Settings from the **Time tracking** and **Work schedules** sections.
- Settings from the **Local fields** and **SLA rules** sections.
||
||
|#

{% endcut %}

### 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/copy-template.svg)</svg> **Copy an existing queue** option.

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

### Select the queue to copy {#select}

Start typing the name of a suitable queue.

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

### Come up with a name and key for the new queue {#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 -->

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

[*resolution]: A resolution is an issue parameter that shows why an issue was closed. For example: **Resolved**, **Won't fix**, or **Duplicate**. You can add resolutions in the queue settings.