The mobile work-management surface for field technicians. TechDesk captures time automatically (the technician confirms every entry), lets techs create their own internal work tickets without leaving the app, plans a week of scheduled work so today's jobs don't get buried, and renders even the most complex conditional forms correctly — all within Jira Service Management.
Everything a field technician needs. Nothing they don't.
Field technicians spend their days on-site, often with poor connectivity, needing fast access to their assigned tickets. TechDesk gives them a focused, mobile-friendly view of exactly what matters.
Stop chasing timesheets. When a ticket moves out of a "working" status, TechDesk derives the time from the ticket's own history and offers it back as a worklog the technician confirms — and can adjust — in one tap. Nothing is ever logged silently: a human vouches for every entry, and the worklog is attributed to the technician. Admin-configured (pick which statuses count as active work).
Starting a second ticket while one is already tracking is blocked by default — the technician is shown which ticket still has the timer running — because it would bill the same minutes twice. Admins can relax this to a warning or switch it off.
Log the work that never had a ticket. One-tap buttons create internal work tickets — "Drive home", "On-site work", "Depot day" — as plain Jira issues, reported by and assigned to the technician, so they land on their own dashboard and time can be logged against them. No portal detour; the summary is generated for them. Admin-configured buttons (project + issue type + optional form).
Paired with DispatchDesk, captured time is split into travel vs on-site (paused time never billed), each editable separately before logging — and confirmed values re-stamp the reporting fields, so a technician's correction stays in sync with your BI.
Real-time ticket list with priority sorting, SLA countdown timers and search-as-you-type filtering.
Today's work, front and centre. Future-dated jobs move to a Planned tab (grouped Tomorrow / Later) so technicians see what's actionable now — a ticket they've already started stays in the main list even if future-dated. Due dates colour-coded at a glance (overdue red, today orange, upcoming purple). Zero setup; works off your Jira due dates.
Your forms, exactly as designed. Deeply nested conditional JSM forms render correctly on mobile — right questions, right branch, including the instructional text you wrote for your technicians, which follows the same conditions. Automatic and invisible.
Dependent dropdowns done properly. Two-level picklists (Country → City, Site → Asset) render as linked pickers on mobile and save correctly to the issue — no empty lists, no lost values. Discovered at runtime from your field config.
Colour-coded countdown timers on every card and detail view — technicians always know what needs urgent attention.
Today's assignments as a list and as map pins, with a per-ticket Navigate hand-off to Waze or Google Maps. One ticket at a time — no planned multi-stop route.
Cached tickets and a local action queue keep work flowing through poor connectivity — changes sync when back online.
Dark mode across the dashboard, following the device preference.
Turn on Suggest mode and pick which statuses count as active work. Optional per-entry cap, and a toggle to hide manual time entry entirely if the automated flow should be the only path. The one-tracked-ticket-at-a-time rule can be relaxed to a warning or switched off.
Define each internal-work button: label, project, issue type, and optionally a form by name (leave blank for a summary-only ticket). The ticket summary comes from an editable template using {label}, {type}, {name} and {date}.
Map Jira custom fields to display labels, with auto-detected field discovery and a dedicated Request Type filter.
Custom app title, logo and full colour palette — every instance can match the hosting organisation.
Per-field AQL filter scopes so asset dropdowns only show relevant objects to each technician.
Define required attachments by status and request type — enforce photo evidence or signed forms on completion.
Statuses, request types and forms are chosen from live project lists instead of typed, so a typo can't silently break a feature — and legacy typed values are flagged to the admin. Settings are grouped by what you're configuring: Setup, Fields & Statuses, Navigation, Ticket Actions, Time Tracking.
All data stored exclusively in Forge KVS — Atlassian's own infrastructure. No external databases or third-party storage. Feedback stays inside your site too: bug reports are admin-only (routed to your support contact), while any technician can send a feature request.
Your data stays in Atlassian. Map base tiles for the Schedule Map load client-side from OpenStreetMap; the per-ticket Navigate button hands off to Google Maps or Waze only when a technician clicks it. No analytics, no automatic third-party transmission.
Least-privilege permissions — the app requests only the scopes it uses, and internal-work ticket creation uses standard Jira write access, not elevated service-desk permissions. Licensing is enforced through your Atlassian Marketplace subscription: free for small teams, paid above.
Comprehensive security and privacy documentation for enterprise reviews. View security page →
The official app shows tickets. TechDesk runs the technician's day — captures time, creates internal work tickets, plans the week, and handles the forms the mobile portal can't.
While your technicians work from TechDesk on the ground, dispatchers get a planning workspace with DispatchDesk — assigning tickets, viewing SLA risk, and computing routes between admin-pinned technician locations and ticket job sites. Together, dispatch → visit → time → worklog is one connected flow: with DispatchDesk, TechDesk's captured time is split into travel vs on-site (paused time never billed), and the technician's confirmed values re-stamp the reporting fields your BI reads. The two apps share Jira as the source of truth; TechDesk does not push location or status data to DispatchDesk.
Learn about DispatchDesk →Free for up to 10 users. Now live on the Atlassian Marketplace.