General questions about Tracker

How do I use Tracker on a mobile device?

Scan the QR code to download the Yandex Tracker mobile app. To learn more about its features, see Yandex Tracker mobile app.

How do I delete an issue?

You can't delete an issue from a queue, but you can close it with a resolution. For example, you can close duplicate issues with the Duplicate resolution or use the Canceled resolution to close issues created by mistake.

To delete the issues you no longer need, move them to a special queue, then delete it:

• Move an issue to another queue Tracker
• Deleting a queue in Tracker

How do I assign an issue to multiple users?

Each issue can have only one assignee. To organize work involving multiple people:

• If multiple users work on an issue one after another, change the assignee as the issue progresses.

• If multiple users work on an issue at the same time, split the issue into sub-issues and specify an assignee for each sub-issue.

• Create a global field with the List of users type and use it in issues. For example, name this field "Co-assignees" and add other people working on the issue. Alternatively, create separate fields for each role, such as "Analyst", "Tester", and "Designer".

  For more information on creating fields, see How to add an issue field

How do I delete a queue?

A queue can be deleted by its owner and Yandex Tracker admins from the startrek-admins group, as well as by users with the Queue management permissions.

To delete a queue:

1. Open the queue page.

2. To the left of the queue name, select → Administration.

3. Go to the Basic settings tab.

4. Click Delete queue.

5. Confirm the deletion.

For more information about deleting a queue, see Deleting a queue.

How do I find the queue owner?

The owner is specified on the Description tab on the queue page. For more information, see List of queue issues.

I don't have access to an issue

Access permissions for issues are determined by the queue settings.

If you don't have access to the queue and its issues, contact the queue owner. The name of the queue owner is usually specified in the Access denied message.

If you can access the queue page but can't view or edit some issues in the queue, these issues may include components with limited access. Make sure also to contact the queue owner.

Issue exceeds the maximum number of events

When you attempt to edit an issue through the user interface or the Yandex Tracker API, you may see a message about exceeding the allowed number of events.

Each time you update an issue, the event tracker increments, with a maximum limit of 11,100 changes for users and 10,100 changes for robots. After reaching the limit, the issue becomes read-only.

To find out the current number of events in an issue, make a Getting issue parameters API request and check the value of the version parameter. For example, for an issue with the TEST-123 key: https://api.tracker.yandex.net/v3/issues/TEST-123.

What limitations exist in Yandex Tracker

Some fields, parameters, and entities in Yandex Tracker have limitations or accept only specific values. This is necessary to ensure data integrity, performance, and security within the system.

Field, parameter, or entity	Limit
Maximum length of one-line text field	32766 characters
Maximum value for fields of Integer type	2147483647
Maximum number of Drop-down list field values	3000 Clicking the field displays up to 10 elements at a time
Maximum size of an attached file	128 MB in the Yandex Tracker interface or via the API
Recommended number of followers per issue	300 If you add more followers, Yandex Tracker may become unstable
Maximum number of actions per trigger	10
Maximum number of triggers per queue	1000
Maximum number of auto actions per queue	100
Maximum number of forms per queue	20
Maximum number of SLAs per group	30

I can't access a specific page in the Yandex Tracker documentation

Some pages are restricted by default. If you see a 403 error in the Yandex Tracker documentation, request the reader+ role for the staff-only group of pages.

If you have no access to IDM, ask your manager to request the role for you.

Why can't I use widgets grouped by the Summaryfield?

The Summary field specifies the issue name. You can assign custom names to issues. Issue summaries are usually unique. If you create a table where rows or columns are grouped by a set of unique values (from the Summary field), the table might be cluttered and difficult to interpret.

When creating new widgets, avoid using the Summary field to group data in rows or columns of pivot tables, or as a key parameter to build issue statistics. In the near future, the option to aggregate or group widget data by the Summary field will be retired. All the widgets with such grouping will be deleted later.

If you have existing widgets grouped by the Summary field and want to keep them, you can:

• Replace your widget with a new widget with an issue list.
• Create an additional field in your issues to store the data you need to build grouped widgets.

Create a new widget

If you need a simple issue list, replace your widget with an issue list widget. To do this:

1. Create a new Issues widget.

2. Fill out the Filter field in the same manner as in your previous widget.

3. In the Columns field, select the issue parameters to display in the table.

4. Fill in the remaining fields and save the new widget.

5. Delete the previous widget.

Create an additional field and set up grouping for it

If you add keywords to issue names to use them for grouping issues in widgets, we recommend creating a separate field for such keywords. You can then set up grouping using the new field instead of the Summary field.

1. Create a new field to store the data that you used to add to the Summary field.

2. When creating issues, simply enter the data for your widget into the new field.

3. In your existing issues, move the data to the new field by an automatic action:

   1. Select Update issues.

   2. Under Filter parameters, click Add condition, select Summary, and specify the issue name or the keyword you use for grouping in the widget.

   3. Click Add new action and select Update fields. Then select the previously created field and paste the issue name to it.

   4. Create similar automatic actions for every possible keyword.

4. If you're creating an issue using an external source (for example, Yandex Forms), make sure to save the widget data to a new field during integration setup.

5. Edit the old widget to specify the new field instead of the Summary field in the settings.

I still have questions. Where can I send them?

You can ask your questions in the chat. On any issue page, click → Support chat in bottom-right corner.

You can discuss your questions with other users in our chat on Telegram .