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

1. In the left-hand panel, click  Queues and select a queue.

2. In the top right corner of the queue page, click  Queue settings.

3. {% include notitle Поля %}

4. Click Create.

5. Select the field type and click Continue.

6. Set parameters for the new field.

   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.

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

7. Click Create.

Copying a local field

To create a copy of an existing local field:

1. In the left-hand panel, click  Queues and select a queue.

2. In the top right corner of the queue page, click  Queue settings.

3. {% include notitle Поля %}

4. Select a field and, on the right, click  → Copy.

   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.

5. Click Create.

Edit a local field

1. In the left-hand panel, click  Queues and select a queue.

2. In the top right corner of the queue page, click  Queue settings.

3. {% include notitle Поля %}

4. Select a field and, on the right, click  →  Edit.

   A window with field parameters opens: change the value as needed and click Save.

5. To change the category of a local field, click → Change category.

   Start typing the new category's name and select the option from the list.

You can also edit the field properties, category, or visibility by making a request to the Yandex Tracker API to edit a local field.

Delete a 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. In the left-hand panel, click  Queues and select a queue.

2. In the top right corner of the queue page, click  Queue settings.

3. {% include notitle Поля %}

4. Select a field and, on the right, click  →  Delete.

You can also configure the global field visibility by making a request to the Yandex Tracker API to change a local field:

• To hide a field, set true for the hidden parameter.
• To restore a field, set false for the hidden parameter.

Using local fields

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

• When selecting an issue filtering parameter, 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, 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 or copy issues with local fields to a different queue, the local field values will be automatically deleted.

• When working with macros, triggers, or auto actions, you need to follow the {{issue.local.<field_key>}} format if you want to insert the value of a local field into a comment, formula, or HTTP request using a variable.