Yandex Tracker

What it is and why

Yandex Tracker is essentially "Jira in Russian": a similar model (queues, sprints, agile boards, a query language), but with a Russian interface, ruble billing and data kept inside Russia. The main reason to pick it: you're a team in Russia, you don't want to mess with VPNs and foreign cards, and you care about data storage being simpler from a 152-FZ standpoint.

How to do it (step by step)

1. Get access through Yandex 360 for business (or Yandex Cloud). You need an organization account. Sign-up and billing are in rubles.
2. Create a Queue (the equivalent of a project). Set the key (DEV), the issue types and the assignees.
3. Configure statuses and transitions (the queue workflow). A basic flow: Open → In progress → In review → Resolved → Closed.
4. Agile board. Create a board on top of the queue, map columns to statuses, add sprints with dates.
5. Fields. Add custom ones (Component, Team, Estimate in hours or story points). Make the ones you need mandatory on transitions.
6. Query language. Filter with Queue: DEV Status: !Closed Assignee: me and save it as a filter for your dashboard.
7. Integrations. Inside Yandex 360: Mail, Disk, Telemost. Outside — via the API and webhooks, or Albato connectors (amoCRM, Bitrix24, Telegram notifications).
8. Automation: triggers and auto-actions in the queue settings (on transition → notify, on creation → assign).

Ready-made recipe

Wiring it to support: a customer writes to the corporate Yandex 360 mailbox → an issue is created automatically in the SUPPORT queue → a trigger assigns the person on duty and sets an SLA deadline → the manager moves it through the statuses → on "Resolved" the customer gets an automatic email → closed issues build up resolution-time statistics for a report to management. All inside the Russian perimeter, billed in rubles.

What it costs (honestly)

The logic: it's billed as part of Yandex 360 for business — per user per month, with entry-level plans that have limits. The free allowance is capped by the number of employees and issues. Exact figures and boundaries are on the Yandex 360 site and they change.

When it fits / when it doesn't

• Fits: a team in Russia that needs a Russian interface and ruble billing; you already use Yandex 360; data localization under 152-FZ matters; you want a Jira-like process without a foreign cloud.
• Doesn't fit: you need the widest possible range of world-class third-party integrations (that's Jira); you don't want to be tied to the Yandex ecosystem; you need maximum workflow flexibility.

Risks and responsibility

A plus under 152-FZ: the data sits inside the Russian perimeter, which makes personal data localization easier. But the responsibility for obtaining consent to process personal data (if issues contain customer data) and for the processing policy itself is still yours. See the section disclaimer.

🤖 Prompt helper

You are a Yandex Tracker implementation consultant. Our team is {size, type of work}. Help me: (1) design a structure of queues and statuses that matches our process; (2) write 8-10 useful filters in Tracker's query language; (3) set up triggers and auto-actions for the routine work; (4) suggest integrations via Albato or the API with our services (CRM, messengers). Give it step by step, including what to click where.