---
metadata:
  - name: generator
    content: Diplodoc Platform v5.54.1
  - property: og:type
    content: article
  - property: article:section
    content: Настроить очередь
  - property: og:title
    content: Локальные поля задач
  - property: article:tag
    content: Сборник инструкций
alternate:
  - https://yandex.ru/support/tracker/en/local-fields.md
  - https://yandex.ru/support/tracker/ru/local-fields.md
  - href: en/local-fields.md
    type: text/markdown
    title: Markdown version
  - href: llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt


# Local issue fields

If you need a new issue parameter that isn't available among system fields in Yandex Tracker, you can add local fields to your queue. You can see the list of system global fields on the [Yandex Tracker settings](https://tracker.yandex.com/admin/fields) page.

A local field can only be used in the issues of the queue it's linked to. The advantage of local fields is that the queue owner can manage them without the risk of affecting the workflows in other queues. Users working in other queues will not see this field in their issues.

## Creating a local field {#add-local-field}

{% note warning "" %}

By default, [only the queue owner](https://yandex.ru/support/tracker/en/manager/queue-access.md) can configure a queue.

{% endnote %}

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click ![](_assets/svg/queues-ni.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 ![](_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/fields.md -->
   Go to the **Local fields** tab.
   <!-- endsource: en/_includes/fields.md -->

1. Click **Create**.

1. Select the field type and click **Continue**.

1. Set parameters for the new field.

    <!-- source: en/_includes/fields.md -->
    Common parameters:

    * **Name**: Try to give short and concise names to your fields.
        If necessary, add a field description.

    * **Name in English**. This name is shown in the English interface of Yandex Tracker.

    * **Category** All Yandex Tracker fields are grouped into categories. Start typing the name of a relevant category. For example, `System`, `Time tracking`, `Agile`, `Email`, or `SLA`.
        For more information about the fields and categories, see [Standard issue fields](https://yandex.ru/support/tracker/en/user/create-param.md#default-fields).

    * A **key** is generated automatically according to its English name.

    Special parameters:

    * **Multiple choice**. Enable this option so the user can enter multiple field values.
        Only for "User list" and "Drop-down list" field types.

    * **Field type**. Specify the field value format.
        Only for "Number", "Date", and "Input field" field types.

    * **Values in a list**. Enter the possible values and their order.
        Only for the "Drop-down list" field type. You can add up to 3000 values to a "Drop-down list" field. Clicking the field displays up to 10 items at a time.
    <!-- endsource: en/_includes/fields.md -->

1. Click **Create**.

<!-- source: en/_includes/fields.md -->
You can only add a limited number of fields. If you want to add more fields, contact [technical support](https://yandex.ru/support/tracker/en/feedback.md) to increase the limit.
<!-- endsource: en/_includes/fields.md -->

## Copying a local field {#copy}

To create a copy of an existing local field:

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click ![](_assets/svg/queues-ni.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 ![](_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/fields.md -->
   Go to the **Local fields** tab.
   <!-- endsource: en/_includes/fields.md -->

1. Select a field and, on the right, click ![](_assets/svg/actions.svg)</svg> → ![](_assets/svg/copy-template.svg)</svg> **Copy**.

    <!-- source: en/_includes/fields.md -->
    A window for creating a new field opens, with the original field parameters already filled in. You'll need to change some parameters to prevent duplicates. These parameters will be highlighted in red.
    <!-- endsource: en/_includes/fields.md -->

1. Tap **Create**.

## Edit a local field {#edit-local-field}


1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click ![](_assets/svg/queues-ni.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 ![](_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/fields.md -->
   Go to the **Local fields** tab.
   <!-- endsource: en/_includes/fields.md -->

1. Select a field and, on the right, click ![](_assets/svg/actions.svg)</svg> → ![](_assets/svg/icon-edit2.svg)</svg> **Edit**.

    <!-- source: en/_includes/fields.md -->
    A window with field parameters opens: change the value as needed and click **Save**.
    <!-- endsource: en/_includes/fields.md -->

1. To change the category of a local field, click ![](_assets/svg/actions.svg)</svg> → ![](_assets/svg/move-local-field.svg) **Change category**.

    <!-- source: en/_includes/fields.md -->
    Start typing the new category's name and select the option from the list.
    <!-- endsource: en/_includes/fields.md -->


You can also edit the field properties, category, or visibility by making a [request to the Yandex Tracker API to edit a local field](https://yandex.ru/support/tracker/en/api-ref/queues/edit-local-field.md).


## Delete a local field {#delete-local-field}

You can't delete a local field, but you can hide it from the Yandex Tracker interface. You can't add a hidden field to an issue.

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click ![](_assets/svg/queues-ni.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 ![](_assets/svg/settings.svg)</svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/fields.md -->
   Go to the **Local fields** tab.
   <!-- endsource: en/_includes/fields.md -->

1. Select a field and, on the right, click ![](_assets/svg/actions.svg)</svg> → ![](_assets/svg/delete.svg)</svg> **Delete**.

You can also configure the global field visibility by making a [request to the Yandex Tracker API to change a local field](https://yandex.ru/support/tracker/en/api-ref/queues/edit-local-field.md):

<!-- source: en/_includes/fields.md -->
- To hide a field, set `true` for the `hidden` parameter.
- To restore a field, set `false` for the `hidden` parameter.
<!-- endsource: en/_includes/fields.md -->

## Using local fields {#features}

Local fields work the same way as global fields, but there are some nuances to consider:

* When selecting an [issue filtering parameter](https://yandex.ru/support/tracker/en/user/create-filter.md#set-conditions), you can only search for a local field in one queue. To do this, enter a queue key and a period before the field name (for example, `DEVS.Tester`). This will help you avoid confusion if you use local fields with the same names in different queues.

* To search for issues by a local field using the [query language](https://yandex.ru/support/tracker/en/user/query-filter.md), enter a queue key, period, and the field name in Russian or English. Then add a colon and the local field value. For example, `DEVS.Tester: "John Doe"`. If the field's name includes several words, enclose the name in double quotes.

* When you [move](https://yandex.ru/support/tracker/en/user/move-ticket.md) or [copy](https://yandex.ru/support/tracker/en/user/clone.md) issues with local fields to a different queue, the local field values will be automatically deleted.

* When working with [macros](https://yandex.ru/support/tracker/en/manager/create-macroses.md), [triggers](https://yandex.ru/support/tracker/en/user/create-trigger.md), or [auto actions](https://yandex.ru/support/tracker/en/user/create-autoaction.md), you need to follow the `not_var{{issue.local.<field_key>}}` format if you want to insert the value of a local field into a [comment](https://yandex.ru/support/tracker/en/user/set-action.md#create-comment), [formula](https://yandex.ru/support/tracker/en/user/set-action.md#section_calc_field), or [HTTP request](https://yandex.ru/support/tracker/en/user/set-action.md#create-http) using a [variable](https://yandex.ru/support/tracker/en/user/vars.md#local-fields).