Adding issue fields
Standard issue fields
The most popular issue fields (settings) are available in Tracker by default. You can see the list of existing fields on the Tracker settings page.
|QA-engineer||The user who is assigned to test the task.|
|Author||The user who created the issue.|
|Possible spam||Spam flag for tasks created by services with integration.|
|End date||Date when the issue was resolved.|
|Start date||Date when the issue was initiated.|
|Deadline||Date by which the issue should be resolved.|
|Boards||A list of boards the issue belongs to.|
|Access||A list of users who have permission to read and edit the issue but don't receive notifications about issue updates.
Access permissions to issues are depend on the queue settings.
|Last update by||Last user to make changes to the issue.|
|Assignee||User handling the issue.|
|Fix Version||Product version that the issue belongs to. The list of available versions is determined by issue settings.|
|Key||Unique issue ID used within its queue. Created automatically.|
|Number of issue comments created in Tracker.|
|Number of issue comments created via email.|
|Components||Tags used to mark and sort issues within a queue.
The list of available components is determined by issue settings.
|Followers||A list of users following the issue. By default, users can view and edit issues and receive all notifications about issue updates.
Access permissions to issues depend on the queue settings.
|Affected Version||Product version that the issue belongs to. The list of available versions depends on the queue settings.|
|A list of users who have been called to comment on the issue. Users are removed from this field as soon as they reply in a comment.|
|Updated||Date and time of the latest issue update.|
|Description||The field describes the issue and explains what has to be done.|
|Queue||Key of the queue that the issue belongs to.|
|Last Comment||Date and time of the last comment in the issue.|
|Priority||The value determines the issue's importance.|
|Voted By||A list of users who voted on the issue.|
|Votes||Number of users who voted.|
|Project||Names of projects the issue belongs to.|
|Resolved||Date and time when the issue was resolved.|
|Mailing lists||Teams and departments subscribed to the issue. By default, these users can view and edit issues and receive all notifications about issue updates.
Access permissions depend on the queue settings.
|Resolution||Reason for closing the issue.|
|Resolver||User who closed the issue.|
|Created||Date and time of issue creation.|
|Status||Current issue progress. Examples:
Testing. For more information, see Setting up issue statuses.
|Last status change||Date and time of issue status update.|
|Tags||Text labels that make it easier to search for issues and sort them. For more information, see Structuring issues.|
|Type||Issue type, such as
Improvement. For more information, see Configuring issue types.
|Time spent||Time that the assignee spent resolving the issue.|
|Estimate||Time that the assignee is planning to spend on the issue. The field value decreases when time spent is specified.|
|Original estimate||The initial estimation of the time it should take to resolve the issue.|
|Story Points||Issue complexity visualized as Story Points. For more information, see Basic concepts of agile development.|
|Sprint||Name of the sprint that the issue belongs to.|
|Email To||A list of email addresses the user specified in the Email To field when sending an email.|
|Email Cc||Email address that the user specified in the Cc field when sending an email.|
|Email From||Sender's email address.|
|Created By email to||Email address that received the message triggering issue creation.|
|SLA||Timer that tracks the timeframe for processing issues in a queue. For example, you can specify the time allowed for the assignee to respond to a newly created issue. For more information, see SLA.|
Adding a local field
If you need to add a new issue field that is not available in Tracker, 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 won't see this field in their issues.
To learn more about creating and using local fields, see Local issue fields.
Local fields are temporarily not supported in certain cases. They will be implemented later. For more information, see Local field constraints.
Adding a global field
Only the administrator can add global issue fields.
To add a new issue field (parameter):
Make sure you are logged in as an administrator.
On the Tracker top panel, select → Configure Tracker.
Go to the Fields tab.
Click Create field.
Select the field type and click Continue.
Set parameters for the new field:
Category. All Tracker fields are grouped into categories. Select the category that best suits the new field.
Name in Russian. Try to give the fields short and informative names.
Name in English. This name is shown in the English interface of Tracker.
Type of number (only for fields with the
List items (only for fields with the
drop-down listtype). Specify the possible values and their order.
Number of list items (only for fields with the
Number of employees (only for fields with the