Custom fields (mileage and address)
Setting up task fields for automatic mileage recording and geofence auto-centering
Taskloc can read and write custom fields of tasks in the tracker. Two scenarios are supported:
| Scenario | What it does |
|---|---|
| Mileage field | When a GPS session stops, the app adds the route distance to a numeric field of the task in the tracker. The total mileage per task accumulates. |
| Address field | When a geofence is created (a site is linked to a task), the app reads a text field and suggests the coordinate as the pin center. No manual search on the map. |
Support by connector
| Connector | Mileage | Address / geofence | Key type |
|---|---|---|---|
| Redmine | ✅ | ✅ | Numeric ID (34) |
| Yandex Tracker | ✅ | ✅ | String key (localField1) |
| Bitrix24 | ⚠️ plan | ⚠️ plan | UF field name (UF_AUTO_1234567890) |
| Kaiten | ⚠️ experimental | ⚠️ experimental | Card property string key |
| OpenProject | ✅ | ✅ | Numeric ID (1) |
| Jira Cloud | ✅ | ✅ | String identifier (customfield_10042) |
| Taiga | ⚠️ no | ⚠️ no | — (the app does not read project custom attributes) |
| GitHub | ❌ | ❌ | — |
| Linear | ❌ | ❌ | — |
| monday.com | ✅ | ✅ | Board column id |
| ClickUp | ✅ | ✅ | Field string id |
| Asana | ⚠️ plan | ⚠️ plan | Field gid |
| Trello | ❌ | ✅ no setup needed | — (the address is a field of the card itself) |
The field key is entered manually (except for Redmine and Bitrix24). The app collects the list of tracker fields automatically only for Redmine and Bitrix24 — there you can pick the field. For the other connectors there is no list to pick from: find the field ID or key in the tracker (instructions below) and enter it in the connector card manually.
Taiga: Taiga itself does have custom attributes, but the app does not work with them — neither mileage to the task nor the geofence center from an address goes through them. Mileage is still calculated and stored in Taskloc and is visible in reports.
GitHub and Linear: they have no custom task fields suitable for mileage and address (in GitHub, fields live on the Projects board item, not on the issue itself). Mileage stays in Taskloc reports, and the geofence center is set manually on the map.
Kaiten: the Kaiten API for custom card properties is still in testing. Writing mileage to Kaiten works on a best-effort basis (it is saved in Taskloc, but is not passed to the tracker if the API returns an error).
Bitrix24: the portal allows creating custom fields in tasks only from the Professional plan and above. On Basic and Standard there are no fields — and so no mileage recording to the task and no geofence auto-centering from an address. This is a Bitrix24 limitation, not a Taskloc one; what stays available is described in If your plan is below Professional.
Asana: custom fields are available only on paid Asana plans (Starter and above). On the free Personal plan there is neither mileage to the task nor geofence auto-centering from an address — mileage stays in Taskloc reports, and the geofence center is set manually. In the settings you enter the field gid, and the field must be added to the task's project.
Trello: the address lives right in the card — no address field key is needed, and the geofence works on any plan. Mileage is not written to the card: that needs a custom field (in Trello — from the Standard plan), and the app does not support writing them yet. Mileage stays in Taskloc reports.
monday.com and ClickUp: the fields are created in the tracker manually and are not limited by plan. In monday.com the address is a Location column and mileage is a numeric column; in ClickUp the address is a location field and mileage is a number field. With a field of another type the write will not work.
How to create a field and find its ID / key
Redmine
- Open Administration → Custom fields.
- Click New custom field → Issues.
- For the mileage field choose the Float type.
- For the address field choose the Text (string) type.
- Save. The field ID is shown in the URL of the edit page:
.../custom_fields/**34**/edit→ ID =34.
Yandex Tracker
- Go to Queue settings → Issue fields → Create field.
- For mileage: the Number type (integer or float). For the address: the Text type.
- Save. The field key (
localField1,localField2, ...) is shown in the list of the queue's fields next to the name.
Bitrix24
⚠️ The Professional plan or higher is required. On lower plans the item for creating a field is unavailable — Bitrix24 will offer to upgrade or to turn on a 15-day trial.
- Open any task and in its card choose Custom fields → Add field.
- For mileage add a field of the Number (decimal) type. For the address — String.
- Save. The system name of the field in the
UF_AUTO_xxxxxxxxxxformat is shown in the list.
About the trial. A field created during the 15-day trial disappears from the portal after the trial ends, while the field key entered in the app stays — mileage writes will be rejected by the tracker. If the trial is over, clear the field keys in the integration card or move to the Professional plan.
OpenProject
- Open Administration → Settings → Custom fields.
- Click Create a new custom field.
- For mileage choose the Float type. For the address — Text.
- Link the field to the work package types you need.
- The field ID is shown in the URL:
.../custom_fields/**1**/edit→ ID =1.
Jira Cloud
- Open Settings (gear) → Issues → Custom fields.
- Create custom field: for mileage — the Number type, for the address — Text field (single line).
- Link the field to the project's screens, otherwise it will not appear in the issue.
- An identifier like
customfield_10042is visible in the URL of the field configuration page (.../ConfigureCustomField!default.jspa?customFieldId=**10042**→ keycustomfield_10042).
Kaiten
- Open Board settings → Card fields.
- Add a numeric property (mileage) or a text one (address).
- The property key is shown in the settings URL or in the API response.
If your plan is below Professional
This applies to Bitrix24: there are no custom fields in tasks on the Basic and Standard plans. What still works and what to do:
| What | How without custom fields |
|---|---|
| Mileage | Calculated and stored in Taskloc as usual — visible in reports and on the "Mileage" page, and can be exported from there. It does not reach the Bitrix24 task card. |
| Geofence center | Set manually on the map when creating the geofence — the app simply does not fill in the coordinate from the address field. |
| Tracker field on completion | Unavailable: there is nowhere to write the value. |
The other features of the connector do not depend on the plan — tasks, status change, comments, time tracking, attachments and site arrival check-in work on any plan.
Address field format
The address field can hold:
- A text address — for example
"1 Main Street, Springfield". The app performs forward geocoding via OpenStreetMap Nominatim. - Ready-made coordinates —
"55.1545,61.3680"(latitude first, WGS-84, comma-separated). The pin center is set without a geocoder request — faster and more precise.
With no network or an unrecognized address, the app silently uses the current location as the pin center — no error is shown.
Setting it up in the app
- Go to Settings → Integrations → your tracker.
- In the Custom fields section enter:
- Mileage field ID (Redmine / OpenProject) or Mileage field key (others)
- Address field ID / Address field key
- Changes are saved when the input field loses focus.
If you are setting up a field for the first time — create it in the tracker, run at least one GPS session (the route must be non-zero), stop it. Open the task in the tracker and check that the field has been updated.
Display
The connector card (Settings → Integrations → your tracker) has a Display section with interface settings. They are set separately for each connector.
| Setting | What it does |
|---|---|
| Show project filter | The project filter section on the tasks screen. On by default. Off → the section is hidden and tasks are shown across all projects. In trackers with different terminology this is a queue / board / group. |
| Manage projects / queues / boards… | Opens the choice of which task containers are visible in the filter and in what order. |
| Filter by components / Filter by tags | Yandex Tracker only: add the "Components" and "Tags" sections to the filter panel. |
Inline editing of task fields in the card (title, description, status and so on) is off by default; there is no longer an "Edit tasks in the app" switch in this section. Completing a task (choosing a status and a comment when stopping a GPS session or the timer) always works.
Send to client (RedmineUP Helpdesk)
If the Helpdesk plugin is installed on the Redmine server, a Send to client switch appears in the comment form and in the task completion window. When it is on, the recipient is shown below the switch — the contact/mailbox the message will go to (determined by the ticket's contact on the server side).