---
metadata:
  - name: generator
    content: Diplodoc Platform v5.47.3
alternate:
  - https://yandex.com.tr/support/tracker/en/manager/add-ticket-type.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt

# Issue types

A queue may include different types of issues, e.g., **New feature**, **Improvement**, or **Error**. Issue types help you distribute work among team members by activity (**New feature**, **Error**, or **Improvement**) or decompose issues ([**Epic**](https://yandex.com.tr/support/tracker/en/manager/epic.md), **Story**, or **Issue**).

The queue owner and users granted [permission to access the queue settings](https://yandex.com.tr/support/tracker/en/manager/queue-access.md) specify:

* Queue issue types
* [Resolutions](https://yandex.com.tr/support/tracker/en/manager/create-resolution.md) for each issue type
* [Workflows](https://yandex.com.tr/support/tracker/en/manager/workflow.md) for each issue type

In Yandex Tracker, there are system types of issues. They are listed in the [Yandex Tracker settings](https://tracker.yandex.com/admin/types). You can use these issue types in any queues. If you don't find a suitable issue type among the default types, [an administrator](https://yandex.com.tr/support/tracker/en/role-model.md#admin) can create a new issue type. It will appear in the issue type list and users will be able to use it in their queues.

## Adding an issue type to a queue {#add-ticket-type-queue}

To add a new issue type to the queue:

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" fill="currentColor" aria-hidden="true" class="yc-icon nv-composite-bar__menu-icon" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M6.702 3.013 8 3.5V2.386A2 2 0 0 1 10.702.513l3.351 1.257A3 3 0 0 1 16 4.579v4.035a2 2 0 0 1-2.702 1.873L12 10v1.114a2 2 0 0 1-2.702 1.873L8 12.5v1.114a2 2 0 0 1-2.702 1.873L1.947 14.23A3 3 0 0 1 0 11.421V7.386a2 2 0 0 1 2.702-1.873L4 6V4.886a2 2 0 0 1 2.702-1.873ZM5.5 6.563l.553.207A3 3 0 0 1 8 9.579v1.319l1.824.684a.5.5 0 0 0 .676-.468V7.079a1.5 1.5 0 0 0-.973-1.405L6.176 4.418a.5.5 0 0 0-.676.468v1.676Zm4.553-2.293L9.5 4.062V2.386a.5.5 0 0 1 .676-.468l3.35 1.256c.586.22.974.78.974 1.405v4.035a.5.5 0 0 1-.676.468L12 8.398V7.079a3 3 0 0 0-1.947-2.809ZM1.5 11.421V7.386a.5.5 0 0 1 .676-.468l3.35 1.257c.586.219.974.779.974 1.404v4.035a.5.5 0 0 1-.676.468l-3.35-1.257a1.5 1.5 0 0 1-.974-1.404Z" clip-rule="evenodd"/></svg> **Queues** and select a queue. {#queue}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/transition-page.md -->
   In the top right corner of the queue page, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon nv-aside-header-footer-item__icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none"><path fill="currentColor" fill-opacity=".85" fill-rule="evenodd" d="M8.875 2.125h2.25a.5.5 0 0 1 .5.5v.23c0 1.925 2.083 3.128 3.75 2.165l.2-.115a.5.5 0 0 1 .682.183l1.125 1.949a.5.5 0 0 1-.183.683l-.2.115c-1.666.962-1.666 3.368 0 4.33l.2.115a.5.5 0 0 1 .183.683l-1.125 1.949a.5.5 0 0 1-.683.183l-.199-.115c-1.667-.963-3.75.24-3.75 2.165v.23a.5.5 0 0 1-.5.5h-2.25a.5.5 0 0 1-.5-.5v-.23c0-1.925-2.083-3.128-3.75-2.165l-.2.115a.5.5 0 0 1-.683-.183l-1.125-1.949a.5.5 0 0 1 .183-.683l.2-.115c1.667-.962 1.667-3.368 0-4.33l-.2-.115a.5.5 0 0 1-.183-.683l1.125-1.949a.5.5 0 0 1 .683-.183l.2.115c1.667.963 3.75-.24 3.75-2.165v-.23a.5.5 0 0 1 .5-.5zm-2 .5a2 2 0 0 1 2-2h2.25a2 2 0 0 1 2 2v.23a1 1 0 0 0 1.5.866l.2-.115a2 2 0 0 1 2.731.732l1.125 1.949a2 2 0 0 1-.732 2.732l-.2.115a1 1 0 0 0 0 1.732l.2.115a2 2 0 0 1 .732 2.732l-1.125 1.949a2 2 0 0 1-2.732.732l-.199-.115a1 1 0 0 0-1.5.866v.23a2 2 0 0 1-2 2h-2.25a2 2 0 0 1-2-2v-.23a1 1 0 0 0-1.5-.866l-.2.115a2 2 0 0 1-2.732-.732l-1.125-1.949a2 2 0 0 1 .732-2.732l.2-.115a1 1 0 0 0 0-1.732l-.2-.115a2 2 0 0 1-.732-2.732l1.125-1.949a2 2 0 0 1 2.732-.732l.2.115a1 1 0 0 0 1.5-.866v-.23zM12.25 10a2.25 2.25 0 1 1-4.5 0 2.25 2.25 0 0 1 4.5 0zm1.5 0a3.75 3.75 0 1 1-7.5 0 3.75 3.75 0 0 1 7.5 0z" clip-rule="evenodd"/></svg></svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. Go to the **Workflows** tab. This tab displays the list of queue workflows along with the issue types and resolutions configured for each workflow.

1. To add an issue type to an existing workflow, click **Add issue type** in the respective workflow section and select the appropriate issue type from the list of system issue types. To learn how to add an issue type to a new workflow, see the [guide on creating workflows](https://yandex.com.tr/support/tracker/en/manager/workflow.md#create).

To set the default type for a queue issue, select one of the options in the **Issue type** field.

## Creating an issue type {#create-ticket-type}

{% note warning "" %}

Only an [administrator](https://yandex.com.tr/support/tracker/en/role-model.md#admin) can create new issue types. Once the issue type has been created, you cannot delete or edit it.

{% endnote %}

You can create a new issue type on the **Issue types** page in the Yandex Tracker settings or on the **Workflows** page in a queue.

{% list tabs %}

- **Issue types** page


   1. Make sure you are authorized in Yandex Tracker as an [administrator](https://yandex.com.tr/support/tracker/en/role-model.md#admin).

   1. In the left-hand panel, select <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" fill="currentColor" aria-hidden="true" class="yc-icon nv-composite-bar__menu-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 17 17"><path d="M15.84 4.69c-.06-.4-.37-.69-.75-.82-.4-.09-.8.04-1.06.29L12.2 6l-1.03-.16L11 4.81 12.84 3c.29-.28.38-.69.29-1.06-.13-.38-.41-.69-.82-.78a4.76 4.76 0 0 0-4.56 1.28A4.72 4.72 0 0 0 6.47 6.9L.72 12.62a2.66 2.66 0 0 0 0 3.63 2.58 2.58 0 0 0 3.62 0l5.72-5.72a4.8 4.8 0 0 0 5.78-5.84Zm-2.34 3.5a3.23 3.23 0 0 1-3.38.81l-.43-.16L3.3 15.2c-.37.4-1.1.4-1.47 0a1.04 1.04 0 0 1-.3-.75c0-.28.12-.53.3-.75l6.38-6.35-.13-.43a3.12 3.12 0 0 1 .72-3.41 3.2 3.2 0 0 1 2.31-1h.04L9.4 4.31l.46 2.82 2.82.5L14.5 5.8c0 .88-.34 1.75-1 2.38ZM2.72 13.75c-.28 0-.47.22-.47.5 0 .25.22.5.47.5.25 0 .47-.25.47-.5.03-.25-.19-.5-.47-.5Z"/></svg></svg> **Administration** → **Issue types**.


   1. Click **Add issue type**.


   1. Fill in the fields as follows:
      * **Name**: Enter a name for your new issue type in Russian.
      * **Name in English**: It will be generated automatically based on the Russian name.
      * **Key**: It will be generated automatically based on the Russian name.

   1. Click **Create**.


- **Workflows** page


   1. <!-- source: en/_includes/transition-page.md -->
      In the left-hand panel, click <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" fill="currentColor" aria-hidden="true" class="yc-icon nv-composite-bar__menu-icon" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M6.702 3.013 8 3.5V2.386A2 2 0 0 1 10.702.513l3.351 1.257A3 3 0 0 1 16 4.579v4.035a2 2 0 0 1-2.702 1.873L12 10v1.114a2 2 0 0 1-2.702 1.873L8 12.5v1.114a2 2 0 0 1-2.702 1.873L1.947 14.23A3 3 0 0 1 0 11.421V7.386a2 2 0 0 1 2.702-1.873L4 6V4.886a2 2 0 0 1 2.702-1.873ZM5.5 6.563l.553.207A3 3 0 0 1 8 9.579v1.319l1.824.684a.5.5 0 0 0 .676-.468V7.079a1.5 1.5 0 0 0-.973-1.405L6.176 4.418a.5.5 0 0 0-.676.468v1.676Zm4.553-2.293L9.5 4.062V2.386a.5.5 0 0 1 .676-.468l3.35 1.256c.586.22.974.78.974 1.405v4.035a.5.5 0 0 1-.676.468L12 8.398V7.079a3 3 0 0 0-1.947-2.809ZM1.5 11.421V7.386a.5.5 0 0 1 .676-.468l3.35 1.257c.586.219.974.779.974 1.404v4.035a.5.5 0 0 1-.676.468l-3.35-1.257a1.5 1.5 0 0 1-.974-1.404Z" clip-rule="evenodd"/></svg> **Queues** and select a queue. {#queue}
      <!-- endsource: en/_includes/transition-page.md -->

   1. <!-- source: en/_includes/transition-page.md -->
      In the top right corner of the queue page, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon nv-aside-header-footer-item__icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none"><path fill="currentColor" fill-opacity=".85" fill-rule="evenodd" d="M8.875 2.125h2.25a.5.5 0 0 1 .5.5v.23c0 1.925 2.083 3.128 3.75 2.165l.2-.115a.5.5 0 0 1 .682.183l1.125 1.949a.5.5 0 0 1-.183.683l-.2.115c-1.666.962-1.666 3.368 0 4.33l.2.115a.5.5 0 0 1 .183.683l-1.125 1.949a.5.5 0 0 1-.683.183l-.199-.115c-1.667-.963-3.75.24-3.75 2.165v.23a.5.5 0 0 1-.5.5h-2.25a.5.5 0 0 1-.5-.5v-.23c0-1.925-2.083-3.128-3.75-2.165l-.2.115a.5.5 0 0 1-.683-.183l-1.125-1.949a.5.5 0 0 1 .183-.683l.2-.115c1.667-.962 1.667-3.368 0-4.33l-.2-.115a.5.5 0 0 1-.183-.683l1.125-1.949a.5.5 0 0 1 .683-.183l.2.115c1.667.963 3.75-.24 3.75-2.165v-.23a.5.5 0 0 1 .5-.5zm-2 .5a2 2 0 0 1 2-2h2.25a2 2 0 0 1 2 2v.23a1 1 0 0 0 1.5.866l.2-.115a2 2 0 0 1 2.731.732l1.125 1.949a2 2 0 0 1-.732 2.732l-.2.115a1 1 0 0 0 0 1.732l.2.115a2 2 0 0 1 .732 2.732l-1.125 1.949a2 2 0 0 1-2.732.732l-.199-.115a1 1 0 0 0-1.5.866v.23a2 2 0 0 1-2 2h-2.25a2 2 0 0 1-2-2v-.23a1 1 0 0 0-1.5-.866l-.2.115a2 2 0 0 1-2.732-.732l-1.125-1.949a2 2 0 0 1 .732-2.732l.2-.115a1 1 0 0 0 0-1.732l-.2-.115a2 2 0 0 1-.732-2.732l1.125-1.949a2 2 0 0 1 2.732-.732l.2.115a1 1 0 0 0 1.5-.866v-.23zM12.25 10a2.25 2.25 0 1 1-4.5 0 2.25 2.25 0 0 1 4.5 0zm1.5 0a3.75 3.75 0 1 1-7.5 0 3.75 3.75 0 0 1 7.5 0z" clip-rule="evenodd"/></svg></svg> **Queue settings**. {#settings}
      <!-- endsource: en/_includes/transition-page.md -->

   1. Go to the **Workflows** tab. It shows the list of workflows in the queue. Select the workflow to add the new issue type to and click <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" class="g-icon" fill="currentColor" stroke="none" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 16 16"><path fill="currentColor" fill-rule="evenodd" d="M2.97 5.47a.75.75 0 0 1 1.06 0L8 9.44l3.97-3.97a.75.75 0 1 1 1.06 1.06l-4.5 4.5a.75.75 0 0 1-1.06 0l-4.5-4.5a.75.75 0 0 1 0-1.06Z" clip-rule="evenodd"/></svg></svg> in the respective workflow line.

   1. Click **Add issue type**, start typing the name of the new issue type, and click the create button.


   1. Fill in the fields as follows:
      * **Name**: Enter a name for your new issue type in Russian.
      * **Name in English**: It will be generated automatically based on the Russian name.
      * **Key**: It will be generated automatically based on the Russian name.

   1. Click **Create**.


   The created issue type will be immediately added to the current queue's workflow. However, you can also use it in other queues.

{% endlist %}

## Removing an issue type from the queue {#delete-ticket-type}

Before removing an issue type from the queue, make sure it is not used in any of the queue issues.

1. Open the queue page.

1. Use filters to [find all the queue issues](https://yandex.com.tr/support/tracker/en/manager/quick-filters.md) that belong to the type you want to remove and change it to any other type the queue supports.

1. In the top right corner of the queue page, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon nv-aside-header-footer-item__icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none"><path fill="currentColor" fill-opacity=".85" fill-rule="evenodd" d="M8.875 2.125h2.25a.5.5 0 0 1 .5.5v.23c0 1.925 2.083 3.128 3.75 2.165l.2-.115a.5.5 0 0 1 .682.183l1.125 1.949a.5.5 0 0 1-.183.683l-.2.115c-1.666.962-1.666 3.368 0 4.33l.2.115a.5.5 0 0 1 .183.683l-1.125 1.949a.5.5 0 0 1-.683.183l-.199-.115c-1.667-.963-3.75.24-3.75 2.165v.23a.5.5 0 0 1-.5.5h-2.25a.5.5 0 0 1-.5-.5v-.23c0-1.925-2.083-3.128-3.75-2.165l-.2.115a.5.5 0 0 1-.683-.183l-1.125-1.949a.5.5 0 0 1 .183-.683l.2-.115c1.667-.962 1.667-3.368 0-4.33l-.2-.115a.5.5 0 0 1-.183-.683l1.125-1.949a.5.5 0 0 1 .683-.183l.2.115c1.667.963 3.75-.24 3.75-2.165v-.23a.5.5 0 0 1 .5-.5zm-2 .5a2 2 0 0 1 2-2h2.25a2 2 0 0 1 2 2v.23a1 1 0 0 0 1.5.866l.2-.115a2 2 0 0 1 2.731.732l1.125 1.949a2 2 0 0 1-.732 2.732l-.2.115a1 1 0 0 0 0 1.732l.2.115a2 2 0 0 1 .732 2.732l-1.125 1.949a2 2 0 0 1-2.732.732l-.199-.115a1 1 0 0 0-1.5.866v.23a2 2 0 0 1-2 2h-2.25a2 2 0 0 1-2-2v-.23a1 1 0 0 0-1.5-.866l-.2.115a2 2 0 0 1-2.732-.732l-1.125-1.949a2 2 0 0 1 .732-2.732l.2-.115a1 1 0 0 0 0-1.732l-.2-.115a2 2 0 0 1-.732-2.732l1.125-1.949a2 2 0 0 1 2.732-.732l.2.115a1 1 0 0 0 1.5-.866v-.23zM12.25 10a2.25 2.25 0 1 1-4.5 0 2.25 2.25 0 0 1 4.5 0zm1.5 0a3.75 3.75 0 1 1-7.5 0 3.75 3.75 0 0 1 7.5 0z" clip-rule="evenodd"/></svg></svg> **Queue settings**.

1. Go to the **Workflows** tab. It shows the list of workflows in the queue. Select the workflow containing the issue type you want to remove.

1. Hover over the line with the issue type to be removed, click the issue type and then click <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" aria-hidden="true" class="yc-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M14 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 14 6.125zm-5.906 0a1.874 1.874 0 1 1 0 3.749 1.874 1.874 0 0 1 0-3.749zM2 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 2 6.125z"/></svg></svg> → **Remove issue type from the queue** in the respective workflow line.
