Connecting trackers
Which 19 trackers connect to Taskloc, where to get access, how they name projects and tasks and what goes back to the tracker — time, comments and statuses
Updated:
Taskloc connects to your task tracker and shows the tasks from it. 19 systems are supported:
| Tracker | How it connects | Where to get access |
|---|---|---|
| Redmine | server address + login/password | your Redmine account (guide) |
| Yandex Tracker | sign-in with Yandex ID (OAuth) | the "Yandex Tracker" button — the browser opens by itself (guide) |
| Bitrix24 | portal address + sign-in with Bitrix24 (OAuth) | the "Bitrix24" button — the browser opens by itself (guide) |
| Jira Cloud | sign-in with Atlassian (OAuth) | the "Jira Cloud" button — the browser opens by itself (guide) |
| Linear | sign-in with Linear (OAuth) | the "Linear" button — the browser opens by itself (guide) |
| Taiga | server address + login/password | your Taiga account (guide) |
| Kaiten | space address + API key | Kaiten profile → API key (guide) |
| OpenProject | instance address + API token | My account → Access tokens → API (guide) |
| GitHub | Personal Access Token | step-by-step guide |
| Pyrus | e-mail + security key | Pyrus profile → security key (guide) |
| Megaplan | portal address + login/password | your Megaplan account (guide) |
| YouGile | login/password + choice of company | your YouGile account (guide) |
| Weeek | personal token | workspace settings → API (guide) |
| Aspro.Cloud | portal address + API key | issued by the portal administrator: System settings → API settings (guide) |
| monday.com | personal token | monday.com profile → Developer → My access tokens (guide) |
| ClickUp | personal API token | Settings → Apps → API Token (guide) |
| Asana | Personal access token | My Settings → Apps → Manage Developer Apps (guide) |
| Trello | API key + token | trello.com/power-ups/admin — you issue both yourself (guide) |
| Wrike | sign in with Wrike (OAuth) | Sign in with Wrike in integrations — the browser opens by itself (guide) |
To connect: Settings → Add tracker (with several organizations — Settings → All trackers (N) → Add tracker) — pick the tracker and follow the prompts. The first tracker is usually connected right at the first sign-in (see First sign-in).
Familiar names
The mobile app speaks the language of your tracker. What Redmine calls a "project" is called differently in other systems — and the filters and cards in the app use the native word. The web dashboard does not use this vocabulary: it shows GPS sessions, routes and reports, and tracker entities are not labeled there.
| Tracker | Task container | Task |
|---|---|---|
| Redmine, OpenProject | project | task |
| Yandex Tracker | queue | task |
| Bitrix24 | group | task |
| Jira Cloud | project | issue |
| Linear | team | issue |
| Taiga | project | issue |
| Kaiten, Trello | board | card |
| GitHub | repository | issue |
| Pyrus | form | task |
| Megaplan, Weeek, Aspro.Cloud, Asana | project | task |
| ClickUp | project (in ClickUp itself — a List) | task |
| YouGile | board | task |
| monday.com | board | item |
| Wrike | project folder | task |
What can each tracker do?
You can start the GPS tracker or the timer, check in and change a task's status in all 19 trackers; time goes back to the tracker in 13 of them, while in Linear, Taiga, GitHub, YouGile, monday.com and Trello it stays only in Taskloc.
The main scenario — find a task → start the GPS tracker or the timer → check in → comment — works the same with every tracker. The differences are in the details (trackers are listed by rows so the table does not run out of width):
| Tracker | Creating a task | Comments | Status change | Time to the tracker | Tags | Attachments | Ready-made filters |
|---|---|---|---|---|---|---|---|
| Redmine | ✅ | ✅ | ✅ | ✅ | — | ✅ | saved queries |
| Yandex Tracker | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | I'm the assignee / author / follower |
| Bitrix24 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | roles (Doing / Helping / Delegated / Watching) + statuses |
| Jira Cloud | ✅ | ✅ | ✅ (workflow) | ✅ (worklog) | ✅ | ✅ | saved filters |
| Linear | ✅ | ✅ | ✅ (workflow state) | ❌ — no time tracking; time stays in Taskloc | ✅ | ✅ | — |
| Taiga | ✅ | ✅ | ✅ (status / board column) | ❌ — no time tracking; time stays in Taskloc | ✅ | ✅ | — |
| Kaiten | ✅ | ✅ | ✅ (board column) | ✅ | ✅ | ✅ | — |
| OpenProject | ✅ | ✅ | ✅ | ✅ | — | ✅ | — |
| GitHub | ✅ | ✅ | ✅ (open/closed or a Projects column) | ❌ — no time tracking; time stays in Taskloc | ✅ (labels) | — | — |
| Pyrus | ✅ | ✅ | ⚠️ only "Open" / "Closed" | ⚠️ as a comment (spent_minutes) | ✅ (lists) | ✅ | — |
| Megaplan | ❌ | ✅ | ✅ (portal action) | ⚠️ as a comment with the time worked | ✅ | ⚠️ viewing only | — |
| YouGile | ✅ | ✅ | ✅ (board column) | ❌ — time stays in Taskloc | — | — | — |
| Weeek | ✅ | ✅ | ✅ (board column + completion) | ✅ | ✅ | ✅ | — |
| Aspro.Cloud | ✅ | ❌ — a note in the "Report" field | ✅ | ✅ (duration only, without start and end) | — | — | — |
| monday.com | ✅ | ✅ | ✅ (board status column) | ❌ — the API does not accept time; time stays in Taskloc | ✅ | ✅ | — |
| ClickUp | ✅ | ✅ | ✅ (List status) | ✅ | ✅ | ✅ | — |
| Asana | ✅ | ✅ | ✅ (section + "completed") | ⚠️ only on a paid Asana plan | ✅ | ✅ | — |
| Trello | ✅ | ✅ | ✅ (list on the board) | ❌ — time stays in Taskloc (optionally as a line in a comment) | ✅ | ✅ | — |
| Wrike | ✅ | ✅ | ✅ (workflow status) | ✅ (in hours, on a date) | — | ✅ | — |
About time entries. The duration of every GPS session and timer is always saved in Taskloc itself — regardless of the tracker. In addition, the time is sent to the tracker (worklog / time tracking) if the tracker supports it and the administrator has turned the time tracking module on. If the module is off, the app does not show an error and the time stays in Taskloc (see FAQ).
About creating a task. The "+" button on the task list creates a task right in the tracker — in all of them except Megaplan. It appears only when the tracker, the team policy and your instance profile all allow it at the same time, and it works only with a network connection — more in Creating a task.
About auto-pause. Auto-pause on inactivity is temporarily unavailable for every tracker: to pause a session without the phone, the server would need access to the tracker, and Taskloc keeps credentials only on the device. A pause set manually is recorded in Taskloc.
About attachments. You can attach files and photos to a task (including several photos at check-in) in every tracker except GitHub, YouGile and Aspro.Cloud; in Megaplan you can see a task's attachments but cannot attach your own yet.
Redmine: error 422 "Issue is invalid"
If sending time to Redmine manually (via the "log time to the task" action) returns 422 "Issue is invalid", this is not an app failure but a refusal by Redmine itself.
- Cause. The Time tracking module is not enabled in Redmine for the project the task belongs to.
- Fix. Redmine administrator: Project → Settings → Modules → check "Time tracking". Then send again.
- What the app does. An entry with error 422 is not retried in a loop — Taskloc shows the reason straight from Redmine and keeps the time saved in Taskloc. You can send it to the tracker after the module is enabled.
Can I track time in several trackers at once?
Yes. Several trackers connect to one Taskloc account — you do not need a second account: a new tracker is added as an integration in the active organization, and your account and data do not change (Account and organizations). The task list combines all of them, and each tracker gets its own tab in the filter panel with its own set of filters. Most users need just one tracker — then there are no tabs and the panel stays as simple as possible.
Time is tracked per task, not per tracker: a GPS session or the timer runs on a specific task, and the time goes to that task's tracker — if the tracker accepts time (see the table above). In Taskloc reports, time on tasks from all trackers is shown together.
Connecting a second tracker in an organization also turns on the app's Advanced mode: screens and buttons do not change with it, the mode is visible in the line under the Advanced mode toggle in Settings and in a one-off notification about the switch — see Simple and Advanced mode.
In this section
Custom fields (mileage and address)
How to set up tracker task fields for Taskloc — mileage added to a numeric field after a GPS session and a site address that centers the geofence, per connector
Redmine — connecting
Connect Redmine to Taskloc with a server address, login and password — tasks, comments, statuses, worklog time and custom fields
Yandex Tracker — connecting
Connect Yandex Tracker to Taskloc via Yandex ID and an Organization ID — tasks by queue, comments, statuses, time entries, tags and custom fields
Bitrix24 — connecting
Connect a Bitrix24 portal to Taskloc via OAuth — tasks by group, comments from the task chat, statuses, tags and time entries; custom fields need Professional
Jira Cloud — connecting
Connect Jira Cloud to Taskloc with one-click OAuth — issues, comments, workflow transitions, worklog time and attachments; Data Center and Server unsupported
Linear — connecting
Connect Linear to Taskloc with one-click OAuth — issues, comments, workflow states, labels and attachments; Linear has no time tracking, time stays in Taskloc
Taiga — connecting
Connect self-hosted Taiga or Taiga.io to Taskloc with a server address, login and password — issues, comments and board columns; time is not written to Taiga
Kaiten — connecting
Connect Kaiten to Taskloc with a space address and an API key from your profile — cards by board, comments, moving across columns, time entries and tags
OpenProject — connecting
Connect OpenProject to Taskloc with an instance address and an API token — work packages by project, comments, statuses, time entries and custom fields
GitHub — connecting
Connect GitHub to Taskloc with a fine-grained personal access token — issues, comments, closing and Projects board columns; time is not written to GitHub
Pyrus — connecting
Connect Pyrus to Taskloc with your e-mail and secret key — Inbox tasks by form, comments, Open or Completed status; time is written as a comment parameter
Megaplan — connecting
Connect Megaplan to Taskloc with a portal address, login and password — tasks, comments and statuses; time goes as a comment and tasks cannot be created
YouGile — connecting
Connect YouGile to Taskloc with a login and password and one company per device — tasks by board, comments and columns; no time entries and no attachments
Weeek — connecting
Connect Weeek to Taskloc with a workspace personal token — tasks by project, comments, board columns, completion and real time entries split by day
Aspro.Cloud — connecting
Connect Aspro.Cloud to Taskloc with a portal address and an administrator API key — tasks, statuses and hours written as a duration; no comments
monday.com — connecting
Connect monday.com to Taskloc with a personal token — items by board, updates, the status column and subtasks; time is not written to monday.com at all
ClickUp — connecting
Connect ClickUp to Taskloc with a personal API token — tasks by List, comments, List statuses and work time written as a real ClickUp time entry without doubles
Asana — connecting
Connect Asana to Taskloc with a personal access token — tasks by project, comments, sections and completion; time and mileage need a paid Asana plan
Trello — connecting
Connect Trello to Taskloc with an API key and a token — cards by board, comments, lists as statuses and the card address for the geofence; no time in Trello
Wrike — connecting
Connect Wrike to Taskloc via OAuth — tasks by project folder, comments, statuses, priority and time in hours on a date; address and mileage need a paid plan