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 TermMeaningJira Equivalent
IncidentSomething brokenIncident request
Service RequestNeed access/helpRequest type
ProblemRoot causeProblem issue
ChangePlanned modificationChange request

Incident vs Service Request (Very Important)

4

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

4

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

PriorityResponse TimeResolution Time
Critical15 min4 hrs
High30 min8 hrs
Medium4 hrs2 days
Low1 day5 days

SLA Setup Logic

4

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

4

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

4

Must-Have Rules

TriggerAction
Ticket createdAssign to team
Waiting for customer 3 daysReminder
Resolved 5 daysAuto close
VIP user ticketHigh 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

💼 Professional Support Available

If you are facing issues in real projects related to enterprise backend development or workflow automation, I provide paid consulting, production debugging, project support, and focused trainings.

Technologies covered include Java, Spring Boot, PL/SQL, CMS, Azure, and workflow automation (jBPM, Camunda BPM, RHPAM, Flowable).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital metal podium     


Comments

Post a Comment

Popular posts from this blog

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more