Local issue fields

If you need to add a new issue field that is not available in Tracker, you can add local fields to your queue. You can see the list of existing global fields on the SettingsTracker 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.

Adding a local field

1. Open the queue page.

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

3. Go to the Local fields tab.

4. Click Create field.

5. Select the field type and click Continue.

6. Set parameters for a new field:

   • Name. Try to give short and concise names to your fields.

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

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

   • Category All Tracker fields are grouped into categories. Start typing the name of the expected category and select the most suitable one from the list. For example, System, Time tracking, Agile, Email, or SLA.

     For more information about the fields and categories, see Standard issue fields.

   • Multiple choice (only for the fields of the "User list", "Drop-down list", and "Input field" types).

   • Field type (only for the fields of the "Number", "Date", and "Input field" types).

   • List items (only for the "Drop-down list" fields): Specify possible values and their order.

7. Click Create field. You'll see a pop-up notification saying "New local field saved successfully", and the new field will be added to the list.

Edit a local field

You can only change a local field's category using the Tracker web interface. To do this:

1. Click to the right of the field description.
2. In the field that appears, start typing a new category and select one of the suggested values.

You can edit other parameters of local fields via Yandex Tracker API.

Delete a local field

You cannot delete a local field.

You can hide a local field in the interface using Yandex Tracker API. To do this, set "visible": false, "hidden": true.

Using local fields

Local fields usually work the same way as global fields. But there are a few things to consider:

• To use the query language to search issues by a local field, specify a queue before the field's key or name.

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

Accessing local fields via the API

The following two types of actions are supported when working with local fields via the Tracker API:

• Assign a value to a local field.

  To get or change the value for a local field of an issue via the API, specify the field ID in the request body, in the following format: 603fb94c38bbe658********--<field_key>: "<new_value_of_local_field>".

  To find out the ID of a local field, run a query that allows you to get a list of local fields in a certain queue.

• Change a local field's parameter, such as its name or description, or multiple parameter values. For more information, see the Tracker API reference.