Jira Service Management: ITSM for Atlassian-native IT and DevOps teams

JSM's incident management module in Premium tier supports the full incident lifecycle: detection (via monitoring tool integration with Opsgenie, PagerDuty, or Datadog), classification (with priority and severity fields that drive SLA timers and notification rules), investigation (with linked issues, affected services from the CMDB, and communication channels), resolution (with documented resolution steps), and post-incident review (structured retrospective tied to the incident record). - Major incident workflows allow incident commanders to coordinate response across teams, with a dedicated incident timeline that records actions taken during the response. - For DevOps teams, the incident-to-engineering escalation path uses Jira Software's issue linking, so the engineer assigned to investigate sees the full incident context without leaving their familiar Jira Software interface.

The change management module in Premium tier provides structured change workflows with risk assessment scoring, approval routing, and calendar-based change scheduling. Changes are classified as standard (pre-approved, low-risk), normal (requires assessment and approval), or emergency (expedited approval path). - The CI/CD integration with Bitbucket Pipelines is the feature that distinguishes JSM's change management from competitors: a deployment pipeline can be configured to require an approved change request in JSM before the deployment proceeds, creating a gating mechanism that enforces change management discipline without requiring developers to leave their deployment workflow.

JSM Premium includes a native CMDB (formerly Insight, now called Assets) that tracks hardware, software, cloud resources, and their dependencies as configuration items. The CMDB supports custom object schemas — meaning organizations can model their infrastructure topology with the entity types and relationships that match their actual environment rather than forcing data into a rigid predefined structure. - Configuration items link to services, which link to incidents and changes — creating the dependency chain that allows impact analysis during incident investigation and risk assessment during change planning. - The CMDB is most valuable when actively maintained and integrated into operational workflows; organizations that populate it once and never update it end up with stale data that undermines the incident and change processes it is meant to support.

The AI virtual agent in Premium and Enterprise tiers operates inside Slack and Microsoft Teams, intercepting service requests and attempting to resolve them using knowledge base content from Confluence before routing to a human agent. - The virtual agent uses Atlassian Intelligence to understand natural language requests, match them against knowledge base articles, and present relevant answers or guided workflows. - The 1,000 included conversations per month in Premium is the consumption limit — each virtual agent interaction counts as one conversation, and overages require upgrading or purchasing additional capacity.

JSM provides a customer-facing service portal where end users and employees submit service requests, report incidents, and browse knowledge base articles. The portal is customizable with branding, organized by request categories, and can be configured with multiple portals for different departments (IT, HR, facilities, legal). - Request workflows route submissions through approval chains, trigger automation rules for common actions (like provisioning a software license), and track progress against SLA timers.

JSM's automation engine uses a visual rule builder (if-this-then-that logic with triggers, conditions, and actions) to automate repetitive service desk operations. Common automation use cases include auto-assigning tickets based on request type or component, escalating tickets that breach SLA thresholds, sending notifications when linked issues are resolved, auto-transitioning tickets through workflow states based on external events, and closing resolved tickets after a configurable waiting period. - The automation engine operates across Atlassian products — a rule triggered by a JSM incident can create a Jira Software issue, post to a Confluence page, or send a Slack notification.

JSM's SLA management allows project administrators to define service level agreements based on request type, priority, customer organization, or custom field values. SLA timers can be configured with business-hour calendars that account for working hours, weekends, and holidays — meaning a 4-hour response SLA submitted at 4 PM on a Friday with a Monday-Friday business calendar pauses over the weekend and resumes Monday morning. - When SLA timers approach or breach their thresholds, escalation rules can trigger — reassigning tickets, notifying managers, or changing priority levels.