Yandex Tracker time tracking and field visit tracking

If your company works in Yandex Tracker, issues live in queues in the Yandex cloud — and there is no point moving them anywhere else. Taskloc attaches to Tracker and adds what field work is missing: a GPS session per issue, the route and a proof of the visit. Worked hours go back to the issue as a time entry.

You connect with Yandex ID — no password is typed into the app. Taskloc cloud data is stored on servers in Russia.

Where field work and Tracker don't match

• Time is logged to issues by hand, from memory, after the fact.
• Travel and work at the client are one indistinguishable number.
• A client visit is confirmed only by the employee's word.
• The day's route isn't kept anywhere, so there is nothing to plan the next trip on.
• For companies with data-jurisdiction requirements, every new service raises the question of where employee locations will be stored.

How Yandex Tracker time tracking works

1. Connect with Yandex ID via OAuth. Authorization happens in the browser; no login or password goes into the app.
2. Right after connecting, enter your Yandex Tracker Organization ID in the connector settings. Without it no issues load — this is where people stumble first, so we say it up front.
3. The employee opens an issue from a queue and starts a GPS session. Time and route are recorded automatically; a check-in marks the visit.
4. When the session stops, a time entry appears on the issue; comments and status changes go there too.

A note on terms: the task container in Yandex Tracker is a queue, and the app uses that word rather than "project".

Supported: browsing issues by queue, creating issues, comments, status changes, time entries, tags, attachments, custom fields. Ready-made filters — "I'm the assignee", "I'm the author", "I'm a follower".

What managers get

• Time on every issue, recorded while the work happened, not reconstructed from memory.
• A check-in as proof of the visit: location, geofence, time, route.
• Mileage and the route of each trip on a map.
• A live team map and per-employee reports in the web dashboard.
• A trip history to return to when a client asks "were you actually there?"

Yandex Tracker connector limitations

• No auto-pause. Pauses are recorded in Taskloc only: the access token lives on the device, and the server can't manage a session without the phone.
• Custom fields are mapped by hand: copy the local field key (for example, localField1) from the queue settings. An automatic field catalog is built only for Redmine and Bitrix24.
• Tracker instances of external organizations are not supported — the organization linked to your Yandex ID is used.
• Routes, reports and analytics need an internet connection. Tasks, comments, the timer and the GPS session work offline and sync when the network returns.

Privacy and jurisdiction

The employee starts the GPS session. While it runs, time and route are recorded; outside a session no location is collected. Stop the shift and you disappear from the team map.

Taskloc cloud data is stored on servers in Russia and processed under Russian personal data law (152-FZ). Employee locations don't end up in a different jurisdiction from the one your Tracker is already in.

Yandex Tracker questions

Where do I find the Organization ID?

It goes into the Taskloc connector settings after you connect; without it the issue queues won't load. Step by step: connecting Yandex Tracker.

Do we type our Yandex password into the app?

No. You connect with Yandex ID: authorization happens in the browser and the app never sees the password.

What of our data goes into Tracker?

Time entries, comments and status changes on issues — exactly what the employee would otherwise enter by hand. Routes, coordinates and check-ins are not sent to Tracker: they stay in Taskloc and are viewed in the web dashboard.

Is there auto-pause like in Redmine?

No. Among all connectors, server-side auto-pause exists only for Redmine, where credentials are deliberately stored on our server. Here pauses are set and recorded in Taskloc.

What happens to time tracking if the employee loses signal?

The session keeps running: start, stop, the timer and comments work offline and queue on the device. Once the connection is back, the entries reach the Tracker issue; routes and reports in the dashboard appear after that sync.

Is there an iPhone app?

No. Field staff use the Android app; managers use the web dashboard in a browser.

The broader problem

If you came looking not for a connector but for a way to see what your field staff are doing, we cover that separately: field employee tracking.

Try it on your queues

Free works forever for one seat. The Team trial gives 14 days and 3 seats, once per account; no card is needed at sign-up and nothing is charged when it ends — the account simply moves to Free.

Team payments are currently accepted only with Mir cards issued in Russia and the CIS and via SBP. If you are elsewhere, contact us and we will look at your case — we can't promise a particular payment method in advance.