The complete guide to IT service management (ITSM)
Before you start, this guide covers:
What IT service management means
Why our customers use Jira Service Management for ITSM, and how Jira Service Management can support different stakeholders within your organization
How Jira Service Management supports core ITSM practices: requests, incidents, problems, and change management
How Assets, knowledge management, and AI-powered automation (including AIOps) support those practices
Service Collection products referenced: Jira Service Management, Assets, Rovo
Other Atlassian products referenced: Confluence, Bitbucket
Reading time: 5 minutes
What is IT Service Management (ITSM)?
IT service management (ITSM) is the set of practices, workflows, and technologies teams use to design, deliver, support, and continually improve technology services. Modern ITSM connects employees, agents, developers, and operations teams so work moves from request to resolution with the right context.
Jira Service Management, part of Atlassian Service Collection, brings ITSM practices, such as service requests, incidents, problems, changes, assets, and knowledge together in one flexible, AI-native service management platform. It helps teams provide a great employee experience while improving service reliability and operational efficiency.
Jira Service Management is Atlassian’s core service management app in Service Collection. It brings Dev, IT, and business teams together to deliver exceptional employee experiences and improve service resilience. Jira Service Management supports a range of use cases, including IT service management, IT operations, engineering support, enterprise service management, and HR service management.
Learn more about Jira Service Management features and pricing
Why use Jira Service Management for ITSM?
One service management platform: Manage requests, incidents, changes, problems, assets, and knowledge in connected workflows.
Built for the enterprise: Support multiple service teams, business units, channels, and governance models without losing flexibility.
Faster resolution: Give agents relevant context, suggested knowledge, automation, and collaboration tools at the point of work.
AI-native service: Enable teams to expand support capacity, accelerate resolution times, and reduce manual overhead across every department with Rovo.
Better employee experience: Make it easy for people to find help, submit requests, track progress, and communicate with service teams.
Connected operations: Link service work to software development, operations, assets, dependencies, and real-time signals.
Continuous improvement: Use reporting and insights to identify trends, reduce recurring issues, and improve service quality.
Who is Jira Service Management for?
Jira Service Management is an IT service management platform for employees, customers, service agents, service owners, change managers, developers, operations teams, IT leaders, and more.
It helps each audience get the right consumer-grade support, context, workflows, and visibility to resolve requests, manage changes, respond to incidents, and improve service delivery.
Audience | What they need | How Jira Service Management helps |
Employees and customers | A simple way to get help and stay informed | Self-service portal, virtual agent, searchable knowledge, and request tracking |
Service agents | Context and efficient ways to resolve work | Queues, SLAs, automation, collaboration, and linked assets and knowledge |
Service owners | Consistent, measurable service delivery | Configurable workflows, approvals, reports, and service-level visibility |
Change managers | Safe, transparent changes | Risk-aware change workflows, approvals, calendars, and deployment context |
Developers and operations teams | Fast collaboration around incidents and changes | Alerts, on-call, incident response, timelines, and connections to delivery tools |
IT leadership | Business outcomes and operational insight | Cross-team reporting, trends, service health, and improvement opportunities |
What are the core ITSM capabilities in Jira Service Management?
Request management
Jira Service Management supports request management with a centralized Help Center, configurable portals, request types, dynamic forms, approvals, queues, routing, SLAs, automation, and more. These features standardize intake, capture the right information up front, and ensure that requests reach the right team for consistent, trackable fulfillment.
Self-service knowledge and Rovo, Atlassian’s AI offering, help users find answers, choose the right request type, and resolve common needs without agent intervention. When human support is required, requests include relevant context and remain visible from submission through resolution—reducing manual work, improving response times, and creating a better employee experience.
Incident management and AIOps
Jira Service Management supports end-to-end incident management within a single connected workflow. Teams can collect and group alerts from monitoring tools, automatically create incidents, route issues through on-call schedules and escalation policies, and coordinate responders with shared context. Service-aware incident records, runbooks, stakeholder communications, status pages, and reporting help teams reduce alert noise, respond consistently, and improve mean time to resolution (MTTR).
Jira Service Management’s AIOps capabilities accelerate every stage of response. AI suggestions surface affected services, related incidents, recent changes, and relevant knowledge, while Rovo Ops investigates likely root causes, recommends next steps, drafts updates, and generates post-incident reviews. By connecting operational, development, and knowledge data, Jira Service Management helps teams resolve incidents faster, reduce manual work, and turn each incident into an opportunity to prevent recurrence.
Problem management
Jira Service Management supports problem management by providing teams with a dedicated space to log, investigate, and track the root causes of recurring incidents. Problem records link directly to related incidents, changes, and assets — so teams can trace patterns across the service graph without manually correlating data.
The AI suggestions panel surfaces similar past incidents and recent changes (commits, deployments, feature flags) that may be contributing factors, accelerating root cause analysis. Rovo Ops can investigate proactively, and auto-generated post-incident reviews capture the root cause, contributing factors, and follow-on action items the moment an incident closes — turning reactive firefighting into a structured, repeatable process to eliminate problems at the source.
Change management
Jira Service Management supports ITSM change management by connecting change requests to development and operations workflows. Teams can automate change records from CI/CD deployments, classify standard and normal changes, assess risk with AI, route approvals, enforce deployment gates, and coordinate work through a shared change calendar. Service context from Assets, incident history, deployment data, and change plans gives approvers the information they need to make informed decisions.
These capabilities help teams deliver changes faster with less manual effort while maintaining governance and auditability. Automated low-risk changes reduce bottlenecks, risk-based approvals and deployment controls lower the chance of disruption, and connected incident and service data helps teams respond quickly when issues occur.
Asset and configuration management
Jira Service Management, paired with Assets (also part of Service Collection), supports ITSM by providing teams with a flexible, centralized repository for hardware, software, cloud resources, applications, services, contracts, and other configuration items. Teams can model objects, attributes, ownership, lifecycle details, and relationships, then connect that context directly to Jira Service Management requests, incidents, and changes. Imports, discovery, templates, automation, and data cleansing help keep records current, consistent, and trustworthy.
The result is faster incident triage, clearer service dependencies, and safer change impact analysis because teams can quickly see what is affected, who owns it, and what depends on it. Assets also improves lifecycle and cost management, reduces operational and compliance risk, and provides the connected, governed data foundation needed for more useful reporting, automation, and AI-assisted ITSM.
Knowledge management
Jira Service Management connects knowledge directly to the service experience through a native integration with Confluence, allowing IT, HR, engineering, and other teams to publish and maintain policies, runbooks, FAQs, and procedures where agents and employees actually need them. When a request comes in, relevant articles surface automatically in the agent view, and employees can find answers through the help center or portal before a ticket is ever created — reducing ticket volume and speeding up resolution across every team type.
Rovo amplifies this further by making knowledge active rather than static. It can search across Confluence and linked sources to surface the right article for a given request, suggest responses grounded in approved content, and help agents draft replies without having to start from scratch.
Enterprise service management
Jira Service Management extends service management beyond IT to teams such as HR, finance, legal, facilities, and procurement, providing easy-to-use enterprise service management capabilities. Business teams can quickly create branded help centers, request forms, workflows, queues, and approval paths with no-code configuration. Employees can submit requests through portals, email, Slack, or Microsoft Teams, while Rovo uses AI to guide self-service, summarize cases, suggest next steps, and draft responses.
By connecting requests with knowledge in Confluence, linked work, assets, integrations, and reporting, Jira Service Management gives teams shared visibility from intake through resolution. The result is faster routing, fewer repetitive questions, better coordination across departments, stronger control over sensitive work, and measurable improvements in service quality and employee experience.
Service management for engineering
Jira Service Management connects development and operations across the software delivery lifecycle. Teams can consistently capture and route requests, link services and dependencies with Assets, and integrate with CI/CD tools such as Bitbucket Pipelines, Jenkins, CircleCI, and Octopus Deploy. Deployments can automatically create change records, apply AI-powered risk assessment, and use approval gates, maintenance windows, and change calendars to coordinate releases safely. Rovo and Rovo Dev provide answers and context in the tools engineers already use, helping them understand approvals, affected systems, testing requirements, and pipeline issues without interrupting their flow.
When issues reach production, Jira Service Management brings alerts, deployment and commit history, service dependencies, and on-call ownership into a shared incident view. AIOps groups related alerts and helps generate incident details and post-incident review drafts, while native schedules, escalation policies, notifications, and Slack collaboration speed response. Together, these capabilities reduce manual work and context switching, improve Dev and Ops collaboration, lower change risk, and help engineering teams deliver and operate software more reliably.
AI-native service with Rovo
Rovo brings contextual, AI-powered assistance into Jira Service Management to help IT teams answer, act, and resolve faster. Grounded in your organization’s knowledge, tools, and history through the Teamwork Graph, Rovo provides always-on self-service in Slack, Microsoft Teams, and the help center, helping employees get answers and complete routine requests without waiting for an agent.
For service teams, Rovo automates the work behind the queue: it triages and routes requests, identifies knowledge gaps, drafts and updates articles, summarizes ticket history, and recommends next steps. With Rovo Service, teams can also resolve qualifying requests end-to-end across connected tools, using supervised or autonomous workflows. The result is an AI-native service experience that reduces repetitive work, accelerates resolution, and lets agents focus on more complex issues while keeping people in control where it matters.
Customer spotlight: Thumbtack
We love how additive Jira Service Management is. It's a full-featured ITSM solution that we can trust equally on the software side.
Jason Kuo, Director of IT Infrastructure, Thumbtack
The results: 180 hours saved per month, 60% annual cost savings, and a 4.9/5 CSAT score since switching to Jira Service Management.
Take a tour
Want a full walkthrough of Jira Service Management’s IT service management capabilities?
Frequently asked questions
What is IT service management (ITSM)?
IT service management is the set of practices, workflows, and technologies teams use to design, deliver, support, and continually improve technology services. It connects employees, agents, developers, and operations teams so work moves from request to resolution with the right context.
What is the difference between ITSM and ITIL?
ITSM (IT service management) is the broad discipline of designing, delivering, supporting, and improving IT services. ITIL is a framework of guidance and best practices that organizations can use to implement and improve ITSM.
Why use Jira Service Management for ITSM?
Jira Service Management brings service requests, incidents, problems, changes, assets, knowledge, and automation together in one flexible platform. It helps teams improve employee experiences, resolve work faster, connect operations, and continuously improve service quality.
How does Jira Service Management help teams manage incidents?
Teams can collect and group alerts, automatically create incidents, route issues through on-call schedules and escalation policies, and coordinate responders with shared context. AI suggestions and Rovo Ops can surface affected services, related incidents, recent changes, relevant knowledge, recommended next steps, and draft communications.
How do Assets and knowledge management improve ITSM?
Assets provides connected information about hardware, software, cloud resources, applications, services, and their relationships, helping teams triage incidents and assess change impact. Knowledge management connects Confluence articles, policies, runbooks, FAQs, and procedures to the service experience so people can find answers and agents can resolve requests faster.
How much does Jira Service Management cost and how does licensing work?
Jira Service Management pricing depends on your edition, the number of agents, and whether you pay monthly or annually. Plans are available as Free, Standard, Premium, and Enterprise; paid pricing is tiered, so the per-agent price typically decreases as your agent count grows. For current rates, use the Jira Service Management pricing page.