JIRA Service Management
Many teams answer requests from other people: employees who need a laptop, customers who report a billing problem, staff who ask for a leave policy. JIRA Service Management gives these teams a help desk built on JIRA. Requesters submit tickets through a simple portal, and agents resolve them in an organized queue.
Layman's View: A Hotel Reception Desk
Guests walk up to reception with all kinds of needs: extra towels, a late checkout, a broken lamp. The desk records each request, sends it to the right staff member, and tracks it until the guest feels satisfied. A service management project does the same job for digital requests.
Customer | v [ Portal: fills a request form ] | v [ Request becomes a ticket ] | v [ Queue: ticket waits for an agent ] | v [ Agent: works and replies ] | v [ Resolved: customer confirms ]
Key Roles
Roles in a Service Project
| Role | Job |
|---|---|
| Customer | Raises requests and follows their progress |
| Agent | Works on tickets and replies to customers |
| Administrator | Builds request types, queues, and rules |
Request Types
A request type is a customer-facing form with plain-language names. Customers pick "Get IT help" and skip technical terms like "incident". Each request type connects to an internal issue type and workflow behind the scenes.
- Get IT help
- Request new equipment
- Report a system outage
- Ask an HR question
Queues
A queue is a filtered list of tickets that agents work through. Queues use JQL, so each team shapes lists to fit its needs.
Typical Agent Queues
| Queue | Shows |
|---|---|
| Unassigned | New tickets without an owner |
| Assigned to Me | Tickets that belong to the viewing agent |
| Waiting for Customer | Tickets that need an answer from the requester |
| Breaching Soon | Tickets that approach a time goal |
Service Level Agreements
A service level agreement, or SLA, sets a time goal for an action. Teams promise a first reply within two hours and a resolution within one business day. A timer on each ticket tracks the goal.
Ticket created --> SLA clock STARTS Agent asks customer a question --> clock PAUSES Customer replies --> clock RESUMES Agent resolves ticket --> clock STOPS
Sample SLA Goals
| Priority | First Response | Resolution |
|---|---|---|
| Critical | 30 minutes | 4 hours |
| High | 2 hours | 1 business day |
| Normal | 4 hours | 3 business days |
Types of Work
IT teams often sort tickets into four groups, a habit borrowed from ITIL, a popular set of service practices.
Common Service Work Types
| Type | Meaning | Example |
|---|---|---|
| Service Request | A routine ask | Install a software tool |
| Incident | An unplanned break or slowdown | Email stops working |
| Problem | The root cause behind repeated incidents | A failing mail server |
| Change | A planned modification | Upgrade the mail server |
Knowledge Base
Teams can link a knowledge base so customers find answers before they raise a ticket. A customer types "reset password" in the portal and sees a guide at once. Fewer tickets reach agents, and customers get answers faster.
Automation and Notifications
Automation rules assign tickets by request type, send reminders when customers stay silent, and close old tickets after a waiting period. Email notifications keep customers informed at every status change.
Software Project vs Service Project
Comparison of Project Purposes
| Point | Software Project | Service Project |
|---|---|---|
| Main users | Developers and testers | Agents and customers |
| Work arrives from | Team planning | Outside requests |
| Key view | Sprint or Kanban board | Queue with SLA timers |
| Success measure | Delivered features | Fast and satisfying answers |
Feature availability depends on the JIRA plan in use.
Summary
JIRA Service Management turns requests into organized tickets. Portals collect requests, queues organize agent work, and SLAs keep response times visible. Request types, knowledge articles, and automation reduce effort on both sides. Teams outside IT, such as HR and facilities, adopt the same model with great results.