Jira time tracking with GPS: worklogs from Android

Some Jira work doesn't happen at a desk. A consultant spends two days at a client's office, an engineer swaps a server in someone else's rack, a technician sets up equipment on site. The issue is in Jira; the hours, the trip and the visit usually aren't — until someone types a number in from memory.

Taskloc is an Android app that sits on top of your Jira Cloud. The employee picks an issue, starts a GPS session, and the app records time, route and the on-site visit, then logs the hours to the issue as a regular worklog. Your issues stay in Jira.

Why field time in Jira is hard to trust

Worklogs are added afterwards, in one lump: "two days at the client, about sixteen hours".
Travel to the customer and work at the customer end up in the same entry.
Nobody opens Jira in a phone browser in a server room just to log thirty minutes.
When a client questions the hours on an invoice, there is nothing to show except someone's word.

How it works

Connect with Atlassian. In the app: "Add tracker" → Jira Cloud → the Atlassian consent screen opens → Accept. No keys or URLs to copy.
Start a session on an issue. The employee opens one of their Jira issues 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 issue.
Stop, and the worklog is there. When the session stops, a worklog is added to the issue. A comment and a status change go to the same issue.

The worklog is an ordinary one — exactly what you would get if the person had logged time in Jira by hand. Anything you already build on worklogs picks these hours up with no extra setup.

What the Jira Cloud connector supports

Feature	How it works in Jira
Create issues	"+" button on the list; the issue type is the first one available in the project
Comments	Plain-text comments on the issue
Status changes	Through the issue's workflow transitions, the same way Jira itself does it
Time	Worklog on the issue
Labels, sub-tasks, priorities	Supported
Attachments	Files and photos, including several photos at check-in
Saved filters	Your Jira saved filters — build one in the browser, use it in the app
Mileage and address	Written to custom fields (`customfield_NNNNN`); the field ID is entered by hand — the automatic field catalog exists only for Redmine and Bitrix24

What managers get

Worklogs recorded while the work was happening, not reconstructed on Friday.
Time on site and travel time — separately, for every issue.
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.

Mixed teams work fine. People in the office keep logging time in Jira the way they always have; people on the road log it through the app. The issue ends up with the same kind of worklogs — the field ones simply come with a route and a visit behind them.

Limitations of the Jira connector

Jira Cloud only (*.atlassian.net sites). Jira Data Center and Server cannot be connected.
If an Atlassian account has access to several Jira sites, the first available site is used. There is no site picker in the app.
Changing the assignee in the app does not reach Jira — silently. There is no error, but the issue stays with the previous person in Jira. The assignee is shown in the list and on the issue card; change it in Jira itself. For the same reason, the "Assign the issue to me on start" toggle has no effect for Jira.
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.

Setup guide: connecting Jira Cloud.

Privacy and access to your Jira

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.

On Jira access: during connection the Taskloc server takes part in exchanging the Atlassian authorization code for a token, but it does not store the token. The token stays on the employee's device, and the app reads and writes issues directly in Jira.

Questions from Jira admins

Do we need to install anything in Jira or from the Marketplace?

No. Taskloc is not an app inside Jira — it's a mobile client on top of it. Each employee connects their own Atlassian account in the Android app, and the app acts on their behalf, with their permissions.

Does Taskloc keep our Jira tokens on its servers?

No. The server only helps exchange the authorization code for a token and does not keep the token. After that it lives on the device.

We run Jira Data Center. Will it work?

No. The connector works with Jira Cloud only; Data Center and Server are not supported.

Why did an issue created in the app get the wrong type?

The app uses the first issue type available in the project. If you need a different one, change the type in Jira after creation, or create those issues in Jira directly.

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 that track work in Jira and still go to customers: implementation and support, office IT services, equipment servicing, network installation. 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 Jira

Connect your Jira Cloud site, install the app on one phone and take one issue from the start of a session to the worklog appearing in Jira. 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.

Jira Cloud time tracking with GPS: worklogs logged from the field