Skip to content
OctodusDocs

Connectors

Yandex Tracker

Your organization's issues in Yandex Tracker: what the agent reads and changes, licenses and queue access, connecting and attaching to spaces, errors.

Last updated:

On this page
  1. What the agent can do
  2. Access and on whose behalf
  3. How to connect
  4. Attaching to spaces
  5. Limits
  6. Troubleshooting

What the agent can do

  • Read: the list of queues, issue search (Tracker query language, a filter or a queue) and a single issue.
  • Change, one issue per call: create an issue, update fields, move it to another status, add a comment.

Access and on whose behalf

The agent acts as the connected Yandex account inside the organization you entered, with Tracker read and write permissions. It sees and changes exactly what that account can: queues the account cannot access are closed to the agent too.

How to connect

  1. Find the organization ID: in Tracker, Administration, Organizations, the ID field.
  2. Open Integrations, Yandex Tracker, enter the ID and choose the organization type: Yandex 360 or Yandex Cloud.
  3. Click Connect Yandex Tracker and allow access at Yandex. Before saving, Octo checks that the account can see that organization.
  4. Attach spaces. The dashboard asks you to confirm: the space's agent will read and change issues as the connected account, and that extends to every member of the space.

Attaching to spaces

One Tracker connection per space. You can connect several organizations. The ways to attach are described in Connecting services to spaces.

Limits

  • Up to 60 Tracker calls per minute per space.
  • Changes are made one issue at a time, with no bulk operations.
  • Queue permissions are managed in Tracker itself.

Troubleshooting

Reading works, but creating or editing issues is refused (403)

The connected Yandex account has no paid Yandex Tracker license. Without a license, Tracker allows reading but refuses to create or edit issues with a 403.

The fix: an admin of the Yandex 360 organization assigns a Tracker license to that account. No reconnect is needed: changes work as soon as the license is assigned. The account also needs access to the queue where the agent creates or edits the issue.

403 on one particular queue
The account has no access to that queue. Grant access in the queue settings in Tracker.
Connecting fails: the organization is unreachable
Check the organization ID and type (Yandex 360 or Yandex Cloud) and that the account belongs to it.
The agent asks the owner to reconnect Tracker
Yandex rejected the token (access was revoked, for example). Reconnect the same account; the attachments are kept.
"No Yandex Tracker is linked to this space"
The space owner links Tracker in the dashboard.
A version conflict or refused fields
The issue changed at the same time, or a field does not fit the queue. Ask the agent to re-read the issue and try again.