Documentation

TechDesk for Jira Service Management

Version 4.34.0 · Last updated: April 2026

Overview

TechDesk is a purpose-built field technician dashboard that runs natively on Atlassian Forge inside Jira Service Management. It gives field technicians a focused view of the tickets assigned to them, with SLA visibility, status transitions, forms, attachments, signature capture, optional route planning, and configurable branding. Because TechDesk shows tickets assigned to the current user, every technician sees their own work without needing separate filters.

Prerequisites

Jira site requirements

Recommended test data

License

The app requires an active license (licensing is enabled in the manifest). During Marketplace review, the evaluation license provided by the review process is sufficient.

Installation

  1. Install the app from the Atlassian Marketplace listing onto your Jira Cloud site.
  2. After installation, open the app via Apps → TechDesk in the top navigation bar. TechDesk registers as a Jira Global Page and opens in a full-page view.
  3. On first launch the dashboard will be empty, because no projects have been configured yet — this is expected. Continue with the configuration steps below.

Testing Instructions (for Marketplace Reviewers)

This section gives reviewers a complete, reproducible path from install to a working dashboard and covers every major feature.

Accessing Settings

  1. From the app's main screen (empty dashboard on first launch), click the gear / cog icon in the header area.
  2. The Settings Hub opens with five cards:
    • Branding & Appearance — logo, colours and app title
    • App Configuration — project keys, request types, forms, field mappings
    • Asset Field AQL — AQL filter scopes for asset custom fields
    • Attachment Rules — file attachment rules with status / request type filters
    • Feedback & Bug Reports — review user-submitted feedback

App Configuration (required — start here)

Open the App Configuration card. It has four sub-tabs: General, Fields & Statuses, Navigation, and Behavior.

General tab (minimum required setup)

FieldWhat to enterWhy
Project Keys Enter your JSM project key (for example SUP) and click "+ Add". Tells the app which projects to load tickets from. Without at least one project key, the dashboard remains empty. Multiple project keys are supported.
Request Type Names (optional) Enter labels such as Hardware Request or Software Request and click "+ Add" for each. These appear as filter chips on the dashboard. Only useful in combination with a "Request Type" field mapping (see Fields & Statuses). Leave empty to skip.
Create Ticket Forms (optional) Enter a label (for example New IT Request) and a URL (the JSM customer portal URL for that request type, for example https://yoursite.atlassian.net/servicedesk/customer/portal/1/group/1/create/10) and click "+ Add". Adds a "Create Ticket" button to the dashboard that opens the given URL.

Fields & Statuses tab

FieldWhat to enterWhy
Field Mappings Click the "Jira Field" dropdown — it auto-loads every custom field from your site. Pick a field, give it a display label, and click "+ Add". Example: Label = Request Type, Jira Field = the custom field that holds your JSM request type (often customfield_10010). Maps Jira custom fields to display labels. Labels appear on ticket cards and in the detail view. The label Request Type is special — it enables the request-type filter on the dashboard.
Closed Statuses Enter status names that mean "closed/done" in your workflow (for example Resolved, Closed, Declined) and click "+ Add" for each. The dashboard has Open / Closed tabs. These status names define which tickets appear under "Closed".
Status Display Order Enter your workflow statuses in the order you want them displayed (for example Open, In Progress, Pending, Resolved). Controls the visual ordering of status badges and navigation buttons.

Navigation tab (optional — for map / GPS features)

This entire tab can be skipped if you don't have Assets / CMDB configured. The app works fine without it.

Behavior tab (optional)

Includes signature capture status triggers, action-required status flagging, and read-only form name patterns.

Save and test

  1. After filling in at least the Project Keys field, click the "Run Test" button at the bottom. This validates your configuration against your live Jira instance and shows pass / warn / fail results for each section.
  2. Click "Save App Configuration". If the app detects issues (for example a project key that doesn't exist) it shows validation warnings and asks for confirmation before saving.
  3. Click "Back to Dashboard" — your assigned tickets should now appear.

Troubleshooting

SymptomCauseFix
Dashboard is empty after install No project keys configured Go to Settings → App Configuration → General, add at least one project key and save.
Dashboard shows "No tickets found" No tickets assigned to you in the configured projects Create tickets in the configured JSM project and assign them to yourself.
Settings page shows "Not authorized" User lacks admin role Ensure the user has Jira Admin or Project Admin permissions.
Forms section is empty on a ticket No Jira Forms (Proforma) attached to that ticket / request type Attach a form via JSM Project settings → Forms.
Navigation button doesn't appear Navigation threshold not configured, or ticket hasn't reached that status Configure the Navigation tab in App Configuration, or transition the ticket past the threshold.

Support

For support enquiries: support@3t-apps.com

Support hours: Monday–Friday, 9:00 AM–5:00 PM CET. Target response time: 1 business day.

Visit Support page → · View full SLA →