Getting Started with Jira Service Management: Queues, SLAs, and Request Types

A service desk turns chaotic requests into a measurable, prioritised queue

Jira Service Management (JSM) extends Jira with everything a service desk needs: a customer portal, SLAs, queues, and approvals. If you support internal teams or external customers, JSM is where requests become trackable work.

The Customer Portal and Request Types

Customers don’t see Jira — they see a clean portal. Each form on the portal is a request type, which maps behind the scenes to a Jira issue type with a friendly name and tailored fields.

  • "I need access to a system" → Access request
  • "Something is broken" → Report an incident
  • "I have a question" → Get IT help

Queues Replace Inbox Chaos

Agents work from queues — saved, prioritised lists built on JQL. A typical setup:

Queue Filter logic
Unassigned status = Open AND assignee is EMPTY
My open tickets assignee = currentUser()
Breaching soon SLA "Time to resolution" breach within 2h

SLAs make response and resolution time visible and accountable

SLAs: Promises You Can Measure

A Service Level Agreement defines a time target, such as "respond within 1 hour, resolve within 8 business hours." JSM tracks the clock automatically, pauses it during Waiting for customer, and flags breaches.

  1. Define your calendars (business hours, holidays).
  2. Create SLA metrics: Time to first response, Time to resolution.
  3. Add goals per priority — critical incidents get tighter targets.

An SLA you don’t report on is just a number. Pair every SLA with a dashboard.

What to Learn Next

  • Automation for auto-assignment and canned responses
  • Approvals for change and access requests
  • Linking JSM to software teams so incidents reach engineers fast

Arivanandhan Chitheshwaran