How to export issue queues to YT
You can export issue queues from Yandex Tracker to YT, a service for the distributed storage and processing of large amounts of data. This might be helpful when you need to build analytics in DataLens.
To export a queue, use a special form; you must be the owner of the relevant queue to do so. The queue exported to YT is synced with the queue in Yandex Tracker every hour. Please note that all queue issues are exported, even those with limited access.
Queues are exported to the HAHN cluster. Each queue can only be exported to a separate folder.
Exporting queues is only available for the internal version of Yandex Tracker https://tracker.yandex.com/ . For the external version of Yandex Tracker that is part of the Yandex 360 for Business services, exporting queues isn't supported.
How to request queue export
Fill out this form to request queue export. When filling out the form:
-
Choose which data should be masked. When exported, this data will be replaced with
#characters. By default, the service masks all text data, such as issue descriptions and comments. To prevent exports of private data, we recommend that you request only masked exports. -
List the keys of the queues you want to export data from.
Filling out the form will create an issue in the QUEUEAPPROVE queue for a Privacy Office audit. This is a required step: we'll process the queue export only after this issue is completed.
Data representation
Exported queues are available in the HAHN cluster, in home/startrek/tables/prod/yandex-team/queue/queue_key. yandex-team includes two subfolders:
-
queue: List of queues with export requested. Each of these queues contains tables with queue entities:
- comments
- components
- issue_events
- issues
- projects
- schema_version
- versions
- worklogs
-
common: List of entities that are common for all queues in Yandex Tracker:
- csi_results
- priorities
- resolutions
- schema_version
- sprints
- statuses
- survey_results
- surveys
- types
- users
Each table uses unique identifiers (id) that are primary keys. If the content of a field is represented as hash, the value itself is stored in another table. To get it, run a JOIN query using this hash as the id value.
Permissions
The STARTREK team members are responsible for exporting queues to YT and keeping them up-to-date. No one else can write data to YT tables and delete data.
The read-approver role is granted to the owners of exported queues. It allows them to approve read permissions for individual employees.
The queue owner must be scrupulous about granting read permissions, since all queue issues are exported, even those with limited access.
Read permissions can be requested via IDM and the appropriate role must be approved by the queue owner. Users with read permissions can view queue tables in the HAHN cluster.
If a queue has no owner, e.g., the previous owner left the job, a new owner should be appointed. This can be done by a queue team member with the permission to edit the settings. If there is no such team member, contact support to have a new owner appointed. To do this, select the following items in the form:
- Issue\problem area: Queues.
- Request type: Access.