How to add an issue field

Standard issue fields

The most popular issue fields (parameters) are available in Yandex Tracker by default. You can see the list of existing fields on the Yandex Tracker settings page.

If you can't find a relevant parameter among them, you can create a new field in your queue. If you want to add a field that will be available in all Yandex Tracker queues, your administrator can create a global field.

List of default fields

Issue field	Description
System
QA engineer	User assigned to test the issue.
Author	User who created the issue.
Possible spam	Spam flag for issues created through services with integration set up.
End date	Date when the issue was completed.
Start date	Date when work on the issue started.
Deadline	Date by which the issue must be resolved.
Boards	List of boards the issue appears on.
Access	List of users who can read and edit the issue but don't receive notifications about issue updates. The issue permissions are determined by the queue settings.
Summary	Issue name.
Modifier	User who last modified the issue.
Assignee	User who will work on the issue.
Fix Version	Product version the issue belongs to. The list of available versions is determined by the queue settings.
Key	Unique ID of the issue within the queue. It is generated automatically.
Number of comments without message	Number of issue comments created in Tracker.
Number of comments with message	Number of issue comments created via email.
Components	Labels that you can use to categorize and sort issues within the queue. The list of available components is determined by the queue settings.
Followers	List of users that follow the issue updates. By default, they have read and edit access, receive notifications about all updates to the issue. Issue access rules depend on the queue settings.
Affected Version	Product version the issue belongs to. The list of available versions is determined by the queue settings.
Pending reply from	List of users summoned to comments. Once the user replies to the comment, their name will be removed from this field.
Updated	Date and time the issue was last updated.
Description	Problem statement: description of what needs to be done.
Queue	Key of the queue that contains the issue.
Last Comment	Date and time the issue was last commented on.
Priority	Importance of the issue.
Voted By	List of users who voted for the issue.
Votes	Number of users who voted for the issue.
Project	Names of the projects the issue belongs to.
Resolved	Date and time the issue was marked as resolved.
Maillists	Teams and departments subscribed to the issue. By default, they have read and edit access to the issue, receive notifications about all updates to the issue. Issue access rules depend on the queue settings.
Resolution	The reason for closing the issue.
Resolver	User who marked the issue as resolved.
Created	Issue creation date and time.
Status	Current progress on the issue. For example: Open, In progress, Testing. For more information, see Setting up statuses.
Last status change	Date and time the issue status was last changed.
Tags	Text labels that make it easier to sort and search for issues. For more information, see Structuring issues.
Type	Type of the issue, for example: New feature, Bug, or Improvement. For more information, see Issue types.
Time Tracking
Time Spent	The time that the assignee spent resolving the issue.
Estimate	The time that the user plans to spend on the issue. As you log time spent, the value in the field decreases.
Original Estimate	Initial time estimates for the issue.
Agile
Story Points	Issue complexity in Story Points. For more information, see Basic concepts of agile development.
Sprint	Name of the sprint the issue belongs to.
Email
Email To	Full list of recipients the user specified in the To field when sending the email.
Email Cc	Email address the user specified in the CC field when sending the email.
Email From	Email address of the sender.
Created By email to	Email address that received the email from which the issue was generated.
SLA
SLA	This timer shows you how much time is left to process issues in the queue. For example, you can set the time within which the assignee has to respond to a new issue. For more information, see SLA.

Local fields

If you need a new issue parameter that isn't available in Yandex Tracker fields, you can add local fields to your queue.

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.

For more information about creating and using local fields, see Local issue fields.

Global fields

To create a new global issue field:

Make sure you are authorized as an administrator.
On the left-hand panel, select Admin settings → Fields.

Click Create.
Select the field type and click Continue.
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.
Click Create.

Copying a global field

To create a copy of an existing global field:

Make sure you are authorized as an administrator.
On the left-hand panel, select Admin settings → Fields.

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.
Click Create.

Editing a global field

Make sure you are authorized as an administrator.
On the left-hand panel, select Admin settings → Fields.

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

A window with field parameters opens: change the value as needed and click Save.
To change the category of a global 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 change the possible global field values.

Delete a global field

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

Make sure you are authorized as an administrator.
On the left-hand panel, select Admin settings → Fields.

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 the field:

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

Was the article helpful?

Logging spent time

Viewing issue change history