Shares the Jira and Confluence platform
Runs on the same Atlassian Cloud footprint as Jira and Confluence. ITSM and delivery teams share identity, admin, automation, and Rovo AI.
Atlassian • Service management
Jira Service Management
Jira Service Management is Atlassian's service management product for IT, HR, facilities, and customer service. Merito delivers the rollout, ITSM configuration, and ESM work around it.
Merito delivers Jira Service Management rollouts for IT service management (ITSM), enterprise service management (ESM), incident management, and change management, and integrates JSM with the rest of your delivery and business ecosystem. We do not sell Atlassian licenses; we deliver the work around them.
- Best for
- IT service management leaders and service owners, Change managers and CAB chairs, Incident commanders and SRE leads
- Hosting
- SaaS
- Time to value
- IT service desks with a single queue and light ITSM are live in two to four weeks. Full ITIL-aligned ITSM (incident, problem, change, request, knowledge) plus ESM typically runs eight to sixteen weeks for initial rollout, with follow-on waves for additional teams.
- Security posture
- FedRAMP Moderate (Atlassian Government Cloud), SOC 2 Type II, ISO 27001 / 27017 / 27018
- Last reviewed
- 2026-04-24
What it is
Jira Service Management in the enterprise stack
Jira Service Management is Atlassian's purpose-built service management product. It runs on the same Atlassian Cloud platform as Jira and Confluence and extends Jira with queues, SLAs, approvals, a customer portal, ITSM practices (incident, problem, change, request, knowledge), and an ESM model for non-IT service teams like HR, facilities, legal, and customer support.
JSM was formerly Jira Service Desk. Atlassian renamed it as the product expanded beyond help desk into full enterprise service management. It now covers traditional IT support, modern incident and on-call response (with Atlassian-managed alerting and Opsgenie integration patterns), enterprise change management, and the self-service portals that absorb request volume.
Merito's work on JSM is typically a rollout, a rescue, or a rationalization. Rollouts for teams new to JSM or moving from legacy ITSM tools. Rescues for existing JSM instances where queues, SLAs, and approvals have drifted. Rationalizations for footprints consolidating multiple help desks, service catalogs, or ESM teams onto one JSM instance.
Merito does not sell Atlassian licenses. Customers buy JSM directly from Atlassian or through an Atlassian Solution Partner. Our role is the delivery work around the subscription: queue and SLA design, ITSM practice configuration, ESM buildouts, integration with Jira, Confluence, Rovo, identity, monitoring, and enterprise systems.
Ideal use cases
- ITSM rollout with ITIL-aligned incident, problem, change, request, and knowledge practices
- Migration from legacy ITSM tools to Atlassian JSM
- Incident management and on-call with JSM alerts and Opsgenie integration patterns
- Enterprise service management (ESM) rollouts for HR, facilities, legal, and customer support
- Consolidating multiple help desks or service catalogs onto a single JSM instance
- JSM integration with Jira, Confluence, source control, and monitoring systems
What it is best at
Where Jira Service Management earns its seat
ITSM and ESM on one product
Supports both classic IT service management and enterprise service management for non-IT teams without a separate product.
Assets included in Standard
The Assets capability (formerly Insight) is included in Standard and above, so configuration management travels with the core product.
Native incident and on-call
Incident management, alerting, and on-call schedules (including Opsgenie-era capabilities) are built into the product or integrated natively.
AI-powered self-service
Rovo AI and AI virtual service agents absorb L1 request volume, triage incoming requests, and suggest resolutions from Confluence knowledge.
Core capabilities
Jira Service Management capabilities, grouped by outcome
IT service management (ITSM)
Core ITIL-aligned practices for IT service delivery.
Incident management
Queues, alerting, on-call schedules, incident commander workflows, and post-incident review.
Problem management
Problem records linked to incidents, root cause tracking, and known errors.
Change management
Change risk scoring, approvals, CAB workflows, and change-failure reporting with Jira automation.
Request management
Service request workflows, customer portal, approval chains, and SLA tracking.
Knowledge management
Confluence-backed knowledge bases surfaced directly in the portal and AI-suggested on requests.
Enterprise service management (ESM)
Service management for non-IT teams on the same platform.
HR service delivery
Onboarding, offboarding, case management, and employee support via customer portals.
Facilities and legal
Request intake, triage, and SLA tracking for non-IT service teams with their own queues and forms.
Customer service
External customer-facing service management with portals, SLAs, and asset visibility.
Shared admin, isolated projects
Centralized admin across ESM teams with per-team project isolation, permissions, and portals.
Assets and configuration
CMDB-style asset tracking included in Standard and above.
Assets (formerly Insight)
Configurable object schemas for CIs, hardware, software, services, and business entities.
Discovery and import
Asset data import from CMDB, IdP, endpoint management, and custom sources.
Impact analysis
Relationships between assets surfaced on incidents and changes for blast-radius assessment.
AI and automation
Rovo AI and Jira automation applied to service workflows.
AI virtual service agent
Conversational agent that resolves L1 requests from knowledge and routes the rest with context.
AI request triage
Rovo-powered classification, priority suggestion, and knowledge lookup on incoming requests.
SLA and automation rules
Jira automation applied to queues, SLAs, escalations, approvals, and cross-product workflows.
Administration and governance
Service governance controls at enterprise scale.
SLAs and OLAs
Configurable SLAs per queue and request type with breach tracking and reporting.
Customer portal branding
Multi-portal experience with per-team branding, announcement, and categorization.
Centralized admin and audit
Atlassian Admin for org-level product, user, and security management; audit retention per edition.
Where it fits in the stack
How Jira Service Management connects to the rest of your landscape
Native Atlassian integrations
NativeFirst-party Atlassian integrations shared across the footprint.
- Jira SoftwareIncidents and changes linked to engineering work items for blast-radius and delivery context.
- ConfluenceKnowledge base articles surfaced in portal and on request views.
- Rovo AIAI-powered virtual service agents, triage, and knowledge search.
- Atlassian GuardIdentity, data security, and AI governance across the footprint.
- Opsgenie capabilitiesAlerting, on-call, and incident response now embedded in JSM.
Certified integrations
CertifiedCommon certified integrations for service management footprints.
- Slack and Microsoft TeamsChat-based request intake, notifications, and incident collaboration.
- PagerDutyExternal on-call and incident response tooling where already in place.
- Okta, Entra ID, PingIdentity provider integration for users and customer portals.
- StatuspagePublic status communication linked to JSM incidents.
Custom and toolchain integrations
CustomCommon custom JSM integrations Merito delivers.
- ServiceNowBidirectional sync with ServiceNow ticketing, CMDB, or change for coexistence scenarios.
- Monitoring and observabilityDatadog, New Relic, Grafana, Splunk, and similar tools wired to alerting and incident workflows.
- HR and identity systemsWorkday, SuccessFactors, BambooHR, and similar tools for ESM request context.
- Endpoint and CMDB sourcesIntune, Jamf, ServiceNow CMDB, and similar sources feeding Assets.
Deployment and implementation
How it rolls out
- Hosting
- SaaS (US, EU, UK, AU, JP, CA, DE, FR, IN, BR, KR, and others (data residency eligible), Atlassian Government Cloud (US public sector, FedRAMP Moderate), Atlassian Isolated Cloud (2026))
- Implementation complexity
- Moderate
- Typical time to value
- IT service desks with a single queue and light ITSM are live in two to four weeks. Full ITIL-aligned ITSM (incident, problem, change, request, knowledge) plus ESM typically runs eight to sixteen weeks for initial rollout, with follow-on waves for additional teams.
- Prerequisites
- Atlassian Cloud organization with admin provisioning
- Identity provider for SSO on Premium and Enterprise
- Existing assets or CMDB source for Assets import
- Notification and on-call endpoints (email, Slack, Teams, SMS, custom webhook)
- What Merito usually handles
- Atlassian-managed SaaS on the same Cloud platform as Jira and Confluence. Data Center edition of JSM exists on the Data Center sunset path alongside Jira Data Center.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- Jira Service Management is subscription-licensed per agent (not per end user). Editions are Free, Standard, Premium, and Enterprise. Assets is included in Standard and above. Premium adds advanced SLAs, 24x7 critical support, the 99.9% SLA, and Rovo AI capabilities. Enterprise adds multi-site consolidation and enhanced governance. Jira Service Management Data Center is on the same Atlassian sunset timeline as Jira Data Center. Merito does not sell Atlassian licenses; procurement runs through Atlassian or an Atlassian Solution Partner.
- Editions and modules
Free
Up to three agents, limited features. Evaluation tier only.
Best for: Small teams evaluating JSM.
Standard
Per-agent pricing with ITSM, queues, SLAs, customer portal, and Assets.
Best for: IT service teams not needing Rovo AI or 24x7 critical support.
Premium
Adds Rovo AI features, 99.9% SLA, 24x7 critical support, advanced incident management, and global automation.
Best for: Enterprise ITSM with incident management, AI triage, or scaled ESM.
Enterprise
Adds unlimited sites, centralized admin, BYOK encryption, and enhanced SLAs.
Best for: Large footprints consolidating multiple ITSM instances or with BYOK requirements.
- Common expansion areas
- Rovo AI virtual service agent on Premium and above
- Atlassian Guard for identity, data security, and AI governance
- Atlassian Government Cloud for FedRAMP Moderate workloads
- ESM buildouts for HR, facilities, legal, and customer service
- Assets scaled beyond IT CIs into enterprise configuration management
Merito services
How Merito helps you win with Jira Service Management
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
JSM Implementation
Greenfield JSM rollouts for IT service management, incident management, change management, and ESM teams.
Explore service02ITSM Migration
Migration from legacy ITSM tools to JSM with data, workflow, and configuration mapping.
Explore solution03DevOps Consulting
JSM integrated with CI/CD, source control, and observability so incidents and changes reflect what is actually shipping.
Explore service04Training and Enablement
Role-based training for JSM admins, agents, incident commanders, and ESM owners.
Explore service05Staff Augmentation
Merito-placed JSM architects, ITSM consultants, and automation engineers embedded with your team.
Explore service06Signature Support
Ongoing admin support for JSM footprints, including SLA design, queue optimization, Rovo and Assets management.
Explore serviceJSM delivery
ITSM is a practice design problem. JSM is the tool.
Most JSM rollouts that underdeliver got queue design right and practice design wrong. Merito runs JSM engagements as ITSM and ESM design with JSM configured around them.
Merito point of view
JSM success is ITSM practice design, not queue design.
Most JSM rollouts Merito sees were configured as a single help desk queue and then expanded outward. That starting shape is cheap but makes ITIL practice alignment (incident, problem, change, request, knowledge) painful later. Designing the ITSM practices on day one, even lightweight, is cheaper than retrofitting them into a queue-first setup.
Assets is the sleeper value in JSM. Because it is included in Standard and above, most enterprises get a functional CMDB without buying a separate product, and most enterprises do not use it. Wiring Assets into incidents and changes is what makes blast-radius analysis and change risk real rather than theoretical.
For ESM rollouts, the mistake is treating it as a JSM project instead of a business process project. HR, facilities, and legal teams need their requests, SLAs, and portals designed to match how they actually work. Merito runs ESM rollouts as business process work with JSM as the tool.
What buyers usually underestimate
- Setting up JSM as a single queue and deferring ITSM practice alignment.
- Ignoring Assets because it looks like a separate product.
- Treating ESM as an IT rollout instead of business process design.
- Carrying legacy ITSM workflow quirks into JSM during migration without rationalizing.
- Activating Rovo virtual agents without knowledge base discipline in Confluence.
Related from Merito
Continue exploring Jira Service Management on Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Jira Service Management FAQs
Consultation request
Talk to Merito about Jira Service Management
Share your current state (greenfield JSM, legacy ITSM migration, existing JSM rescue, ESM buildout) and the practices you need to run. A Merito Atlassian specialist follows up within one business day.
Practice first, tool second
ITSM and ESM design
Incident, problem, change, request, and knowledge designed around how your team actually operates, not a generic template.
Across the Atlassian footprint
JSM, Jira, Confluence, Rovo
We run JSM as part of the wider Atlassian Cloud footprint so knowledge, delivery, and service work connect.
Next step
Design incident, change, request, and knowledge once.
A Merito JSM engagement starts with the practices your team actually runs. Tell us whether this is a rollout, a migration from legacy ITSM, or a rescue.