Triage Yandex Tracker queues and file issues from chat
Connect Yandex Tracker to the AI agent: queues, issues, sprints, boards and comments. The agent files issues and shows what is overdue and stuck.
How the agent works with Яндекс Трекер
The agent calls the Tracker API at api.tracker.yandex.net and its first question is who it is connected as: that determines which queues are visible to it at all. From there it pulls issues, comments, checklists, links, sprints, boards and projects and works out what the interface makes you piece together by eye: what is overdue, what has no assignee, who is carrying the most and where issues are stuck without movement.
Tracker is built around queues, and those are not merely folders: each has its own set of fields, its own statuses and its own workflow. An issue can only be moved along a transition the queue allows — the API will not accept an arbitrary status — so the agent checks the available transitions before editing rather than after a rejection. The second boundary is the organization: an account may belong to several, and a queue in a neighbouring one simply does not exist for this connection.
On the write side the agent files an issue in the right queue with a description, assignee, priority and due date, moves it through statuses, adds comments, updates checklists and logs time to the worklog. A comment and a status change are visible to the whole team and trigger notifications, so bulk changes — moving a batch of issues, reassigning owners — are shown as a list and carried out only after you confirm.
Access is confirmed with a code on the Yandex ID page, and requests run on behalf of the work account and within its permissions. The tracker:read and tracker:write scopes are requested, but the role in the organization has the last word: a scope grants nothing extra, it only keeps the token inside rights the account already has. Issues are fetched through a search query on the Tracker side, page by page, rather than by walking queues, so a large project answers as fast as a small one. It holds the request rate itself, and when a queue is invisible because of permissions or the organization it names the reason directly.
Integration scenarios
Going through the queues
The agent collects issues from your queues and shows what is overdue, what has no assignee and who is carrying the most.
An issue straight from the conversation
The agent files an issue in the right queue with a description, assignee, priority and due date, right out of the chat discussion.
Sprint summary
On a schedule the agent sends the sprint results: what closed, what rolls over and where issues are stuck without movement.
Statuses, comments and time
The agent moves an issue through statuses, adds a comment, updates the checklist and logs spent time to the worklog.
Who is blocking whom
The agent walks the issue links and shows the blocking chains: which issue is holding the rest, who is working on it and how long it has stood still.
Where the hours went
The agent collects worklog entries for the period and shows how many hours landed on each project, queue and person, and where nothing was logged at all.
Яндекс Трекер examples
В SUPPORT 63 открытых задачи, 11 просрочены.
- Без исполнителя висят 8 — все заведены на прошлой неделе
- Больше всего нагрузки на Кирилле: 19 задач, из них 5 просроченных
- Четыре задачи не двигались 20+ дней, статус «В работе»
Очередь SUPPORT
Document · DOCXHow to connect
Before you connect
- A Yandex ID account that belongs to the organization with Tracker
- The Full access or Administrator role to create and edit issues
- The queues you need live in the same organization as the account
- 1
Sign in to Tracker with your work Yandex ID
Open tracker.yandex.ru under the account whose issues you need: API calls run on its behalf. A personal Yandex ID outside the organization sees no queues.
- 2
Make sure the account is not read-only
Without an active Tracker subscription the default role is read-only: issues are visible but not editable. Writing needs full access or administrator.
- 3
In the queue's Access grant issue viewing
In Queues open a queue → settings icon → Access: grant issue viewing, plus editing for changes. Only the queue owner or an admin can.
- 4
Check the org in Administration
Tracker always works in the context of an organization: Administration → Organizations shows which one the account belongs to. The queues must live there too.
FAQ
With a Yandex ID confirmation code: click Connect, enter the code on the Yandex page and confirm access with your work account. API requests run on behalf of that user and within their permissions in the organization.
Queues, issues, comments, checklists, links, sprints, boards and projects — exactly the ones open to the connected user in the queue's access settings.
Yes, if the user has Full access or Administrator. The Read-only role, which is the default without a Tracker subscription, allows viewing issues and nothing more.
Either the queue is not open to the user in its access settings, or it belongs to another organization: the organizations an account belongs to are listed under Administration, Organizations.