Pyrus time tracking with GPS: duration on the task, no manual entry
Updated:
Pyrus keeps requests and approvals in order, but it can't see where the work happened or how long it took when the person wasn't at a desk. Taskloc is an Android app on top of your Pyrus. The employee opens a task from their Inbox, starts a GPS session, and the app records time, route and the on-site visit. When the session stops, the duration goes to the task.
Your tasks stay in Pyrus. There is no second task system and nothing to migrate.
Why field time in Pyrus is hard to trust
- The request is closed, but whether the technician was on site is known only to the technician.
- Hours are recalled afterwards, as one number for the whole day.
- Travel to the site and work on site end up as one figure.
- The day's route is not kept anywhere.
How it works
- Connect. Your Pyrus account e-mail plus the secret key. Employees get the key themselves in Pyrus: Profile settings → Authorization → Secret key. No administrator is needed.
- Start a session on a task. The employee opens a task from their Inbox and starts a GPS session.
- Let it record. Time and route are written automatically. A check-in records the visit — location, geofence, photos attached to the task.
- Stop, and the duration is on the task. When the session stops, a comment with the duration is added to the task.
How time reaches Pyrus, in plain words
Pyrus has no separate time log. So Taskloc writes time where Pyrus itself accepts it: the session duration goes to the task as the spent_minutes parameter of a comment, together with the completion note — one comment.
You will not see a separate time entry with a start and an end in Pyrus. The full picture of the shift — when it started, when it ended, which route was driven — stays in Taskloc and is visible in its reports.
What the Pyrus connector supports
| Feature | How it works in Pyrus |
|---|---|
| Tasks | Inbox tasks, filtered by form — in Pyrus a form plays the role of a project |
| Create tasks | "+" button on the list |
| Comments | Comments on the task |
| Status | Two values, "Open" and "Completed", changed with a comment carrying the complete / reopen action |
| Tags | Pyrus lists act as tags |
| Attachments | Files and photos on the task |
| Assignee | Can be changed from the app |
| Time | Duration as the spent_minutes comment parameter |
| Mileage and address | Written to form fields, addressed by field name |
What managers get
- Duration on the task, recorded while the work was happening, not typed in at the end of the week.
- Time on site and travel time — separately, for every task.
- The route of each trip on a map, mileage as a number.
- A check-in as proof of the visit: location, geofence, route.
- A live team map and per-employee reports in the web dashboard, which runs in the browser.
Limitations of the Pyrus connector
- Time is a comment parameter, not a separate entry. That is how Pyrus works: it has no time-entry object.
- Automatic status change on tracking start and stop is off. Pyrus has no intermediate "in progress" state, and stopping GPS would close the task.
- Approval steps are not treated as a status and do not appear in the "Status" field.
- Pyrus has no priority field, so the app shows no priorities for it.
- No idle auto-pause: pauses are set in Taskloc only. Server-side auto-pause with notes on the issue is a Redmine connector feature — see time tracking for Redmine.
- Cloud Pyrus is supported.
Setup guide: connecting Pyrus.
Privacy and access to your Pyrus
The employee starts the GPS session. Outside an active session the app does not collect location at all: stop the session and you disappear from the team map. Who sees what is set by team policies.
The secret key is stored on the employee's device, and the app reads and writes tasks directly in Pyrus.
Questions about Pyrus
Where do I get the secret key?
In Pyrus: Profile settings → Authorization → Secret key. Every employee takes their own; no administrator is needed.
Do we need to install anything in Pyrus?
No. Taskloc is not an extension inside Pyrus — it's a mobile client on top of it. Each employee connects their own account in the app, and the app acts on their behalf, with their permissions.
Why is time a comment and not a time-log entry?
Because Pyrus has no time log. The only place Pyrus accepts time is the spent_minutes parameter of a comment, so that is where Taskloc writes it.
Why doesn't the task move to "in progress" when a session starts?
A Pyrus task has only two states — open and completed. Automatic status changes would close the task when GPS stops, so they are off for Pyrus. Complete the task yourself when the work is done.
Several Pyrus accounts use my e-mail. What do I do?
When connecting, open "Advanced" and enter your user ID: the number after #pp in your profile address.
Is there an iPhone app?
No. The field app is Android-only; the manager's web dashboard opens in any browser, including on a phone.
Who it's for
Teams whose requests live in Pyrus while the work happens on site: equipment service and maintenance, facility operations, installation, field support. If visits are the core of the job and the tracker is secondary, see field employee tracking and field service visit tracking.
Try it on your Pyrus
Connect Pyrus, install the app on one phone and take one task from the start of a session to the comment with the duration appearing in Pyrus. Free works forever for one seat; the Team trial gives 14 days and 3 seats, once per account, with no card required. When the trial ends, the account moves to Free — nothing is charged.
Team is paid with Mir cards issued in Russia and the CIS and via SBP, or — with a card issued by a foreign bank — by a one-off Robokassa invoice: contact us and we will send a payment link.
Try the Team plan for 14 days with three seats — no card, no sales call.
Try free for 14 days