Copy queue

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

View the settings that will be copied

Will be copied	Will not be copied
Settings from the Workflows section: transition rules between statuses for different issue types, available resolutions. 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.

Start creating a queue

1. In the left panel, select  Queues, then click at the top.
2. Select the Copy an existing queue option.

Select the queue to copy

Start typing the name of a suitable queue.

Come up with a name and key for the new queue

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.

Confirm queue creation

Check the settings and click Open queue. The new queue will appear in the Queues section of the left panel.

A status is an issue parameter that shows the current stage of the issue. For example , , .

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.

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.