Jira Service Management Series — Part 2
From ITIL Concepts to Real Support Automation in Jira Service Management
This part moves beyond basics and shows how real IT support teams design their service desk — properly structured requests, SLAs, approvals, and automation.
You’ll learn:
ITIL mapped inside Jira Service Management
Designing clean request types & forms
SLA configuration (real example)
Approval workflows (step-by-step)
Automation rules that reduce tickets
1) Understanding ITIL Concepts Inside JSM
Jira Service Management is built around ITIL — but simplified.
| ITIL Term | Meaning | Jira Equivalent |
|---|---|---|
| Incident | Something broken | Incident request |
| Service Request | Need access/help | Request type |
| Problem | Root cause | Problem issue |
| Change | Planned modification | Change request |
Incident vs Service Request (Very Important)
Incident → Email not working → urgent
Service Request → Need VPN access → planned
Mixing these is the #1 mistake in companies
2) Designing Request Types & Forms Properly
Badly designed portals create chaos.
Goal
User should not think → system should guide
Recommended Request Type Structure
IT Support
├── Access Request
├── Software Installation
├── Hardware Issue
├── Network Issue
└── New Employee Setup
Form Design Rules
Golden Principles
Ask minimum questions
Use dropdowns (not text)
Conditional fields
Never expose internal fields
Bad Form Example
“Describe your problem”
Good Form Example
Device Type
Error Message
Location
Urgency
3) SLA Configuration Explained (Real Example)
Most admins configure SLA but never understand it.
Scenario — Laptop Not Working
| Priority | Response Time | Resolution Time |
|---|---|---|
| Critical | 15 min | 4 hrs |
| High | 30 min | 8 hrs |
| Medium | 4 hrs | 2 days |
| Low | 1 day | 5 days |
SLA Setup Logic
SLA = timer running on issue conditions
Important Concepts
Start: Ticket created
Pause: Waiting for customer
Stop: Resolved
4) Workflow & Approval Design (Step-by-Step)
Approvals should not be emails — they must be controlled states.
Example — Software Installation Approval
Workflow
Open → Manager Approval → IT Work → Done
Key Rules
Approval before work starts
Reject returns to requester
Auto close after completion
5) Automation Rules for IT Support Teams
Automation converts service desk into scalable system.
Essential Automations
Must-Have Rules
| Trigger | Action |
|---|---|
| Ticket created | Assign to team |
| Waiting for customer 3 days | Reminder |
| Resolved 5 days | Auto close |
| VIP user ticket | High priority |
Recommendation Section (Production Setup Guide)
Priority Matrix
Impact + Urgency = Priority
Never let users select priority directly.
Mandatory Governance Rules
✔ Separate Incident & Service Request projects
✔ Approval only for financial/security requests
✔ SLA pause when waiting for user
✔ Automation for repetitive actions
Real Enterprise Structure
Level 1 → Helpdesk
Level 2 → Application Team
Level 3 → Engineering
What You Achieved After Part-2
You can now:
Implement ITIL in Jira properly
Design clean portal forms
Configure working SLAs
Build approval workflows
Automate IT support operations
Next Part
Part-3 — Jira Service Management — Advanced Implementation Series
💼 Need Help with Camunda, Jira, or Enterprise Workflows?
I help teams solve real production issues and build scalable systems.
Services I offer:• Camunda & BPMN workflow design and debugging • Jira / Confluence setup and optimization • Java, Spring Boot & microservices architecture • Production issue troubleshooting
🔗 View Services: https://shikhanirankari.blogspot.com/p/professional-services.html
📩 Email: ishikhanirankari@gmail.com | info@realtechnologiesindia.com
✔ Available for quick consulting calls and project-based support✔ Response within 24 hours
🎥 Learn IT with Shikha on YouTube
Prefer learning through videos? Watch practical tutorials on Kafka, Camunda, Alfresco, Java, Spring Boot, Microservices and Enterprise Architecture.▶ Subscribe to Learn IT with Shikha on YouTube
Comments
Post a Comment