You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Jira Service Management Community!
I’m Lisa and I’m a Product Marketing Manager on the Jira Service Management team. In this spirit of JSM June, the team wanted to make sure you’re on your A-game with three interconnected ITSM practices: incident management, change management, and problem management. This post will include an overview of each of the aforementioned practices, how to get started, best practices, and resources to dive in even deeper.
Without further ado, let’s jump in!
Incident management is the process used by DevOps and IT Operations teams to respond to an unplanned event or service interruption and restore the service to its operational state.
- Incident: An unplanned interruption to a service or reduction in the service quality.
- Major incident: An incident with significant business impact, requiring an immediate coordinated resolution.
Jira Service Management provides an Information Technology Infrastructure Library (ITIL) compliant incident management workflow called ISD: Incident Management workflow for Jira Service Management. We recommend you start with this workflow and adapt it to your business needs over time.
Set up your profile to get notifications [video]
Set up a response team [video]
Assign an owner team to a service [video]
Level-up your incident management response [documentation]
Handbook: Atlassian Incident Management Handbook
Change management—also known as change enablement—is an IT practice designed to minimize disruptions to IT services while making changes to critical systems and services.
A change is adding, modifying, or removing anything that could have a direct or indirect effect on services.
Common types of changes:
Standard change: Pre-approved changes that are low risk, performed frequently, and follow a documented process. For example, adding memory or creating a new instance of a database.
Normal changes: Non-emergency changes that require further review and approval by the CAB, such as migrating to a new data center or making performance improvements.
Emergency changes: Changes that arise from an unexpected error or threat that needs to be addressed immediately. Think implementing a security patch or dealing with a server outage.
Treat each change differently based on the level or risk, and draw on data from previous changes to make better decisions going forward. Over time, by leveraging data, you’ll be able to use pre-approvals and automation to ship changes faster without compromising on risk.
Changes help you record, review, and approve changes so your teams can quickly deploy changes and minimize risk.
Connect your CI/CD pipeline [video]
Make the most of change management [documentation]
Problem management is the process of identifying and managing the causes of incidents, in order to reduce the number and impact of future incidents.
Please let us know if this type of content is helpful, and don’t hesitate to share any of your own best practices!