Field days aren't only customer jobs: technicians drive to the office for parts, attend training, drive home. Many teams track these as tickets in a dedicated Jira project — DispatchDesk treats that as a first-class pattern.
Add the project key(s) under Settings → Project Configuration → Internal work projects, and make sure the internal project's workflow statuses are mapped to phases (Settings → Statuses) — internal tickets position by real status transitions exactly like customer jobs.
Internal tickets appear on the Schedule on the technician's row, marked with a ⚙ gear in neutral grey — visually subordinate to customer work. They deliberately stay off the Board, SLA Risk and Today views: they're the technician's day, not dispatchable customer work. On the Map, an internal ticket that resolves to a location is woven into the technician's route and live-status line.
Map a "drive-home flag" field (Settings → Field Mappings) and DispatchDesk recognises those tickets as going to the technician's own home — the Map routes them home, and completing the ticket moves their pin home. Company locations configured under Settings → Locations can be referenced from tickets via a "location reference" field, so a "Drive to Office" ticket inherits the office's coordinates without retyping addresses.
The Map's technician popup has one-click "Move to office / Move home" buttons that simply reposition the pin — no ticket involved. Both approaches coexist fine: quick buttons for ad-hoc moves, internal tickets when you want the time on the Schedule.