Adding issue fields

  1. Issue settings
  2. Adding issue fields

Issue settings

The most popular issue settings are available in Tracker by default. If you don't see the settings you need, your company's admin can create them for you.

Parameter Description
System

Followers

Logins or names of users subscribed to the issue.

By default, followers have access to read and edit the issue and are notified of any changes to it.

Access rules depend on the queue settings. Check with the queue owner.

Access

By default, users in this group have access to read and edit the issue, but they do not receive notifications of changes to the issue.

Access rules depend on the queue settings. Check with the queue owner.

Maillists

Teams and departments that are subscribed to the issue.

By default, members of these teams have access to read and edit the issue and receive notifications of changes.

Access rules depend on the queue settings. Check with the queue owner.

Start date

Date when progress started on the issue. You usually don't need to fill this in when creating an issue.

End date

Date when the issue was completed. You usually don't need to fill this in when creating an issue.

Deadline

Date by which the issue should be resolved.

Tags

Tags are text labels that make it easier to find and sort issues.

Components

You can mark issues with special labels called components. Use them to sort issues within a queue.

The list of available components is defined in the queue settings.

Affected version

The version of the product that the issue is related to. The list of available versions is defined in the queue settings.

The Affected version field is typically used with the Bug type of issue.

Fix version

The version of the product that the issue is related to. The list of available versions is defined in the queue settings.

The Affected version field is typically used with the Bug type of issue.

Time tracking

Original estimate

Initial estimation of time needed for the issue. Time is specified in the format 1w2d3h.

Agile

Sprint

The name of the sprint that the issue belongs to.

Story Points

Estimated effort for the issue in terms of Story Points.

Parameter Description
System

Followers

Logins or names of users subscribed to the issue.

By default, followers have access to read and edit the issue and are notified of any changes to it.

Access rules depend on the queue settings. Check with the queue owner.

Access

By default, users in this group have access to read and edit the issue, but they do not receive notifications of changes to the issue.

Access rules depend on the queue settings. Check with the queue owner.

Maillists

Teams and departments that are subscribed to the issue.

By default, members of these teams have access to read and edit the issue and receive notifications of changes.

Access rules depend on the queue settings. Check with the queue owner.

Start date

Date when progress started on the issue. You usually don't need to fill this in when creating an issue.

End date

Date when the issue was completed. You usually don't need to fill this in when creating an issue.

Deadline

Date by which the issue should be resolved.

Tags

Tags are text labels that make it easier to find and sort issues.

Components

You can mark issues with special labels called components. Use them to sort issues within a queue.

The list of available components is defined in the queue settings.

Affected version

The version of the product that the issue is related to. The list of available versions is defined in the queue settings.

The Affected version field is typically used with the Bug type of issue.

Fix version

The version of the product that the issue is related to. The list of available versions is defined in the queue settings.

The Affected version field is typically used with the Bug type of issue.

Time tracking

Original estimate

Initial estimation of time needed for the issue. Time is specified in the format 1w2d3h.

Agile

Sprint

The name of the sprint that the issue belongs to.

Story Points

Estimated effort for the issue in terms of Story Points.

Adding issue fields

Restriction. Only the company admin can create a new field.

The most popular issue settings are available in Tracker by default. To add a new field:

  1. Make sure that you are logged in as the admin in Yandex.Connect.

  2. Choose  → Tracker settings on the upper panel.

  3. Go to the Fields tab.

  4. Click Create field.

  5. Select the field type and click Next.

  6. 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 will be shown in the English interface of Tracker.

    • Type of number (only for fields with the “number” type).

    • List items (only for fields with the “dropdown list” type). Specify the possible values and their order.

    • Number of list items (only for fields with the “dropdown list” type).

    • Number of employees (only for fields with the “user list” type).

  7. Click Create.