General questions about Tracker
- How to migrate data from Yandex 360 for Business to Yandex Cloud Organization
- How to use Tracker on a mobile device
- How to add colleagues to Tracker
- How to grant or revoke full access in Tracker
- Can you help us with implementation or migration from another service?
- How to delete an issue
- How to delete a queue
- Can an issue have multiple assignees?
- I do not have access to an issue
- How can I find the queue owner?
- Why cannot I use widgets grouped by the Summary field?
- How do I disable automatic sign-out for a federated user account?
- I still have questions. Who do I ask them to?
How to migrate data from Yandex 360 for Business to Yandex Cloud Organization
Since March 1 2021, when connecting Yandex Tracker, an organization is created automatically in Yandex Cloud Organization. The administrator can add to the organization an identity federation so that employees can use their work accounts to log in to Tracker. The use of Tracker is billed through the Yandex Cloud billing.
If Tracker is connected to March 1, the service is linked to an organization in Yandex 360 for Business. We will gradually migrate all organizations from Yandex 360 for Business to Yandex Cloud Organization with no effort needed from your organization's administrator. We will notify your administrator about migrating to Yandex Cloud Organization in advance.
How to use Tracker on a mobile device
The Tracker mobile app is available:
-
In the Google Play
for mobile devices running Android version 8.0 and higher. -
In the App Store
for mobile devices running iOS 11.0 and higher. -
In Huawei AppGallery
, for mobile devices running HarmonyOS. -
As an APK file
for Android.
Learn more about the mobile app.
How to add colleagues to Tracker
You can invite your colleagues who have Yandex accounts to Tracker directly from the service interface.
If your company has a corporate user management system (for example, Active Directory), you can set up identity federation to authenticate via SSO so that your colleagues can use their work accounts to log in to Tracker.
To make sure that the added users can create and edit issues, you need to set up full access for them.
How to grant or revoke full access in Tracker
You can manage user access in the Tracker interface under Manage users.
Note that the total cost of using the service depends on the maximum number of users that had full access to Tracker during a given month. That is why we recommend first to revoke access from the users that no longer need it and then to grant access to new users.
Can you help us with implementation or migration from another service?
We will help you select a proper partner for Tracker implementation. If you want to connect more than 100 users to Tracker, we will refund you part of the implementation cost.
How to delete an issue
You cannot delete an issue, 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. For more information about issues, see Working with issues.
Tip
You can delete a queue and all the issues in it: Move the issues you do not need to a special queue and then delete it.
How to delete a queue
Only the user who has access to editing the queue parameters can delete the queue. Usually, this is the queue administrator or owner.
To delete a queue:
-
Open the queue page.
-
To the left of the queue name, select → Administration.
-
Go to the Basic settings tab.
-
Click Delete queue.
-
Confirm the deletion.
For more information about deleting a queue, see Deleting a queue.
Can an issue have multiple assignees?
An issue can only have one assignee at a time. There are several ways to organize the work of 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.
For more information about issues, see Working with issues.
I do not have access to an issue
Access permissions for issues are determined by the queue settings.
If you do not have sufficient rights to access the queue page and its issues, contact the queue owner or admin. The name of the queue owner is usually specified in the access restriction message.
If you can access the queue page but some of the issues remain inaccessible, these issues may include components with limited access. Make sure also to contact the queue owner.
How can 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.
Why cannot I use widgets grouped by the Summary field?
The Summary field includes the issue name: this is 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 (the Summary field), the result would be cumbersome and uninformative.
Do not use the Summary field to group data in rows or columns of pivot tables, or as a key parameter to build issue statistics. We will soon disable data aggregation or grouping by the Summary field in widgets. All the widgets with such grouping will be deleted later.
If you have any widgets with grouping by the Summary field and you want to preserve 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:
-
Create a new Issues widget.
-
Fill out the Filter field in the same manner as in your previous widget.
-
In the Columns field, select the issue parameters to be shown in the table.
-
Fill in the remaining fields and save the new widget.
-
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. Then instead of the Summary field, you can use this new field for grouping.
-
Create a new field to store data that you add to the Summary field.
-
When creating issues, enter the data needed to build the widget into the new field immediately.
-
In your existing issues, move the data to the new field by an automatic action:
-
Select Issue update.
-
Under Filter settings, click Add condition, select Issue, and specify the issue name (the keyword used for grouping in the widget).
-
Click Add new action and select Update fields. Then select the previously created field and paste the issue name to it.
-
Create similar automatic actions for every possible keyword.
-
-
If you use an external source to create an issue (e.g., Yandex Forms) when setting up integration, save the widget data to a new field.
-
Edit the old widget: use the new field instead of the Summary field in the settings.
How do I disable automatic sign-out for a federated user account?
If a federated user signs out of their account automatically, this may be due to the federation settings. When a session is over, a user logs out of the system and needs to log in again.
These settings can be changed by the organization owner or administrator. To disable automatic sign-out for a user:
- Go to the page of the Yandex Cloud organization that Tracker is enabled for.
- In the left-hand panel, select the Federations tab and click the name of the federation the user belongs to.
- In the top-right corner of the page, click Edit.
- Disable Mandatory re-authentication (ForceAuthn) in IdP and click Save.
I still have questions. Who do I ask them to?
Tracker users can ask their questions using the feedback form