---
metadata:
- name: generator
content: Diplodoc Platform v5.47.3
alternate:
- https://yandex.com.tr/support/tracker/en/faq.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt
# General questions about Tracker
## How can I quickly find answers to frequently asked questions? {#support-center}
In **Information** on the left panel, you can quickly navigate to popular instructions, view keyboard shortcuts, launch a quick guide for Yandex Tracker, and contact support.
## How do I pay for Tracker? {#paying}
Fees for using Yandex Tracker are debited from your [Yandex 360 for Business organization's account](https://yandex.com/support/yandex-360/business/purchase/en/pay/how-to-pay).
The payment amount depends on the number of organization employees and may grow during the month if their number increases.
For more information about pricing, see [Yandex 360 Help](https://yandex.com/support/yandex-360/business/purchase/en/pay/how-to-pay#section_calc).
## How do I use Tracker on a mobile device? {#mobile}
{.border-yes}
Scan the QR code to download the Yandex Tracker mobile app. To learn more about its features, see [About the mobile app](https://yandex.com.tr/support/tracker/en/mobile.md).
## How do I add my colleagues to Tracker? {#add-users}
To add users to Tracker, invite employees to your [Yandex 360 for Business](https://admin.yandex.com) organization. [Yandex 360: How to add employees ](https://yandex.com/support/business/users.html#add-users)
If your company has a corporate user management system (for example, Active Directory), you can [set up identity federation](https://yandex.com/support/yandex-360/business/admin/en/sso.html) to authenticate via SSO so that your colleagues can use their work accounts to log in to Tracker.
## How do I migrate to Tracker from other services? {#migration}
For instructions on how to import data about your projects and issues to Tracker, see [How to migrate to Tracker from other services](https://yandex.com.tr/support/tracker/en/import.md).
## How do I delete an issue? {#delete-ticket}
You cannot delete an issue from a queue, but you can close it with an appropriate resolution. For example, you can close duplicate issues with the **Duplicate** resolution or use the **Canceled** resolution to close issues created by mistake.
If you want to erase unnecessary issues, move them to a special queue and then delete it:
- [Move an issue to another queue Tracker](https://yandex.com.tr/support/tracker/en/user/move-ticket.md)
- [Deleting a queue in Tracker](https://yandex.com.tr/support/tracker/en/manager/delete-queue.md)
## How do I assign an issue to multiple users? {#more-responsibles}
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 [```](https://yandex.com.tr/support/tracker/en/user/create-param.md)
## How do I delete a queue? {#delete-queue}
A queue can be deleted by its [owner](https://yandex.com.tr/support/tracker/en/manager/queue-team.md) and Yandex Tracker administrators, as well as by users with the [`Queue settings` permission](https://yandex.com.tr/support/tracker/en/manager/queue-access.md#permissions).
To delete a queue:
1. Open the [queue page](https://yandex.com.tr/support/tracker/en/user/queue.md).
1. To the left of the queue name, select → **Administration**.
1. Go to the **Basic parameters** tab.
1. Click **Delete queue**.
1. Confirm the deletion.
For more information about deleting a queue, see [Delete queue](https://yandex.com.tr/support/tracker/en/manager/delete-queue.md).
## How do I find the queue owner? {#queue-owner}
The owner is specified on the **Description** tab on the queue page. For more information, see [List of queue issues](https://yandex.com.tr/support/tracker/en/user/queue.md).
## I don't have access to an issue {#no-access}
Access permissions for issues are determined by the [queue settings](https://yandex.com.tr/support/tracker/en/manager/queue-access.md).
If you do not have sufficient rights to access the queue page and its issues, contact the queue owner or [administrator](https://yandex.com.tr/support/tracker/en/role-model.md). The name of the queue owner is usually specified in the access restriction 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](https://yandex.com.tr/support/tracker/en/manager/queue-access.md#access-components). Make sure also to contact the queue owner.
## What limitations exist in Yandex Tracker {#limits}
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 (for each 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](manager/about-forms-integration.md) per queue | 20 |
| Maximum number of SLA rules per queue | 30 |
## Why can't I use widgets grouped by the **Issue** field? {#widgets}
The **Issue** field contains the issue name — an arbitrary value the user comes up with. The names are almost always unique. If you try to build a table where rows or columns are grouped by a set of unique values (in the **Issue** field), the result would be cumbersome and uninformative.
Do not use the **Issue** field to group data in rows or columns of [pivot tables](https://yandex.com.tr/support/tracker/en/user/summary-table.md), or as a key parameter to build [issue statistics](https://yandex.com.tr/support/tracker/en/user/issues-stat.md). We will soon disable data aggregation or grouping by the **Issue** field in widgets. All the widgets with such grouping will be deleted later.
If you have any widgets with grouping by the **Issue** field, and you want to preserve them, you can:
* Replace your widget with a [new widget with an issue list](#replace-widget).
* [Create an additional field](#create_new_field) in your issues to store the data you need to build grouped widgets.
#### Create a new widget {#replace-widget}
If you need a simple issue list, replace your widget with an [issue list widget](https://yandex.com.tr/support/tracker/en/user/tasks.md). To do this:
1. Create a new [**Issues** widget](https://yandex.com.tr/support/tracker/en/user/edit-dashboard.md).
1. Fill out the **Filter** field in the same manner as in your previous widget.
1. In the **Columns** field, select the issue parameters to be shown in the table.
1. Fill in the remaining fields and save the new widget.
1. Delete the previous widget.
#### Create an additional field and set up grouping for it {#create-new-field}
If you add keywords to issue names to use them for grouping issues in widgets, we recommend creating a separate field for such keywords. Then instead of the **Issue** field, you can use this new field for grouping.
1. [Create a new field](https://yandex.com.tr/support/tracker/en/user/create-param.md) to store the data that you add to the **Issue** field.
1. When creating issues, enter the data needed to build the widget into the new field immediately.
1. In your existing issues, move the data to the new field by an [automatic action](user/create-autoaction):
1. Select **Update issues**.
1. Under **Filter parameters**, click **Add condition**, select **Issue**, and specify the issue name (the keyword used for grouping in the widget).
1. Click **Add action** and select **Change field values**. Then select the previously created field and copy the issue name to it.
1. Create similar automatic actions for every possible keyword.
1. If you're creating an issue using an external source (for example, [Yandex Forms](https://yandex.com/support/forms/create-task.html)), make sure to save the widget data to a new field during [integration](https://yandex.com.tr/support/tracker/en/manager/forms-integration.md) setup.
1. [Edit](https://yandex.com.tr/support/tracker/en/user/edit-dashboard.md#edit) the old widget: use the new field instead of the **Issue** field in the settings.
## How do I disable automatic sign-out for a federated user account? {#disable-auto-log-out}
If a federated user signs out of their account automatically, this may be due to the [federation](https://yandex.com/support/yandex-360/business/admin/en/sso.html) settings. When a session is over, a user logs out of the system and needs to log in again.
## I still have questions. Who do I ask them to? {#other-questions}
Ask your question in the chat: on any issue page, click → **Support chat**.
You can also discuss your questions in our [Telegram community ](https://t.me/yandextracker). {#chat}