---
title: "How to add an issue field in Yandex Tracker"
description: "From this article, you'll learn how to add an issue field in Yandex Tracker. The fields can be global or local. You can use preset fields or create custom ones."
---
# How to add an issue field
The most popular issue fields (parameters) are available in Yandex Tracker by default. If you can't find a relevant parameter among them, you can create a new field in your queue. [How to create a local field](#local-field)
If you want to add a field that will be available in all Yandex Tracker queues, {% if audience == "external" %}your administrator can create a global field. [How to create a global field](#global-field){% else %}submit a request to create a global field using [this form](#global-field).{% endif %}
You can see the list of all global fields on the [Yandex Tracker settings](https://tracker.yandex.com/admin/fields) page.
{% cut "List of default fields" %}
#|
|| **Issue field** | **Description** ||
|| **System** | ||
|| QA engineer | User assigned to test the issue.||
|| Author | User who created the issue. ||
{% if distr != "on-prem" %}|| Possible spam | Spam flag for issues created through services with [integration](../manager/queue-mail.md) set up. ||{% endif %}
|| 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.<br/><br/>The issue permissions are determined by the [queue settings](../manager/queue-access.md). ||
|| 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](../manager/versions.md) 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. ||
{% if distr != "on-prem" %}|| Number of comments with message | Number of issue comments created via [email](../manager/queue-mail.md). ||{% endif %}
|| Components | Labels that you can use to categorize and sort issues within the queue.<br/><br/>The list of available [components](../manager/components.md) 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.<br/><br/>Issue access rules depend on the [queue settings](../manager/queue-access.md). ||
|| Affected Version | [Product version](../manager/versions.md) the issue belongs to. The list of available versions is determined by the queue settings. ||
|| Pending reply from | List of users [summoned to comments](comments.md#call-comment). Once the user replies to the comment, their name will be removed from this field. ||
|| Updated | Date and time the [issue was last updated](history.md). ||
|| Description | Problem statement: description of what needs to be done. ||
|| Queue | [Key of the queue](../manager/create-queue.md#key) 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](votes.md). ||
|| Project | Names of the [projects](../manager/project-new.md) the issue belongs to. ||
|| Resolved | Date and time the issue was marked as {% if audience != "internal" %}[resolved](../manager/create-resolution.md){% else %}resolved{% endif %}. ||
|| 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.<br/><br/>Issue access rules depend on the [queue settings](../manager/queue-access.md). ||
|| **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](../manager/workflow-status-edit.md). ||
|| 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](../structure.md). ||
{% if audience == "internal" %}|| Goals | Goal in the [Goals](https://goals.yandex-team.ru) service that depends on this issue's completion. ||{% endif %}
|| Type | Type of the issue, for example: **New feature**, **Bug**, or **Improvement**. For more information, see [{#T}](../manager/add-ticket-type.md). ||
|| **Time Tracking** | ||
|| Time Spent | The time that the assignee [spent resolving the issue](time-spent.md). ||
|| Estimate | The time that the user plans to spend on the issue. As you log [time spent](time-spent.md#show-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](../manager/agile.md#dlen_sp). ||
|| Sprint | Name of the [sprint](../manager/create-agile-sprint.md) 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](../sla-head.md). ||
|#
{% endcut %}
## Local fields {#local-field}
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 information about creating and using local fields, see [{#T}](../local-fields.md).
## Global fields {#global-field}
Global fields can be used in issues across all Yandex Tracker queues.
{% if audience == "external" %}
To create a new global issue field:
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#admin) %}
1. Click **Create**.
1. Select the field type and click **Continue**.
1. Set parameters for the new field.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#params) %}
1. Click **Create**.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#limits) %}
### Copying a global field {#copy}
To create a copy of an existing global field:
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#admin) %}
1. Select a field and, on the right, click  → **Copy**.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#window-1) %}
1. Tap **Create**.
### Editing a global field {#edit-global-field}
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#admin) %}
1. Select a field and, on the right, click  →  **Edit**.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#window-2) %}
1. To change the category of a global field, click  →  **Change category**.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#move) %}
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](../api-ref/issues/patch-issue-field-value.md).
### Delete a global field {#delete-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.
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#admin) %}
1. 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](../api-ref/issues/patch-issue-field-value.md):
{% include notitle [Поля](../_includes/fields-6376855ff2ed.md#del-or-rec) %}
{% else %}
If you need to create a new issue field, we recommend [adding a local field](../local-fields.md) linked to a specific queue. Only create global fields if you can't use a local field.
Global fields are global objects, just like [issue types](../manager/add-ticket-type.md), [issue statuses](../manager/workflow-status-edit.md), and [system resolutions](../manager/create-resolution.md).
{% include [global-objects](../_includes/global-objects-5624503677a8.md) %}
To add a new global issue field, request it using the [form](https://forms.yandex-team.ru/surveys/66769/). Requests are reviewed within 2-3 business days. If your issue is urgent, set its priority to critical and provide a comment on why it is urgent.
{% endif %}
Was the article helpful?
Previous