Managing changes with your IT service desk
Change management process
The IT Service Desk template connects certain requests to a change workflow. We set up the workflow to complement the following change management process. Use the workflow to transition change request records alongside these ITIL recommended activities:
We recommend you start with this workflow and adapt it to your needs over time.
The ITIL change management process, in brief:
- An internal IT member requests a change. They note details like the affected systems, possible risks, and expected implementation.
- The change manager or peers determine if the change will be successful. They may ask for more information in this step.
- After review, the team plans how to put the change in place. They record details about:
- the expected outcomes
- ways to roll back the change
- Depending on the type of change and risk, a change approval board (CAB) may need to review the plan.
- The team works to implement the change, documenting their procedures and results.
- The change manager reviews and closes the implemented change. They note whether it was successful, timely, accurately estimated, within budget, and other details.
Setup for change management in JIRA Service Desk
Configure the workflow and fields with the Change Management workflow add-on
We used the ITIL framework for change management to build a workflow for JIRA Service Desk: https://marketplace.atlassian.com/plugins/com.atlassian.servicedesk.change/server/overview.
You can use this add-on as a template to help you build your own change management process.
To use the workflow from the Marketplace:
- Log in as a user that has the JIRA administrator global permission, and follow the instructions listed here to import a workflow.
- To add the workflow fields to your change issues, activate the screen by following the instructions here: Defining a screen.
Change management workflow
Coordinate changes with a calendar
With Confluence, you can schedule changes. Use Team Calendars to track changes, and schedule change to coincide with business events. Try Team Calendars for Confluence for free.
To set up a change calendar with Team Calendars for Confluence:
- In Confluence, go to your team's space.
- From the sidebar, select Calendars.
- Select Add calendar.
- Viewing the calendar, select Add event.
- Select the Event Type drop down and choose JIRA Issue Dates.
- Under Display, select the JQL (advanced) and enter the following:
project = "Your IT service desk project name" AND issuetype= Change
- Under Date range, select Add start and end date… Select Change start date as the start date. Select Change completion date as the end date.
- Select OK .
The calendar automatically picks up the start and end dates of change requests from your service desk . Then, it plots them on the calendar.
Default form fields for change requests
JIRA Service Desk allows you to customize the fields of information collected from customers. Additionally, you can customize the fields of information used by your agents. JIRA Service Desk does this through issue type fields and screens. Fields help agents assess, approve, and categorize the request for reporting or querying.
By default, we include the following fields in your agent's view of a change request. If needed, you can add custom fields. Find out more about fields in JIRA.
|Summary||A short description of the request.|
|Reporter||The person who submitted the request.|
|Component/s||Segments of your IT infrastructure that relate to the request. For example, "Billing services" or "VPN server". These are used for labeling, categorization, and reporting.|
|Attachment||Files or images added to the request.|
|Description||A long, detailed description of the request.|
|Linked Issues||A list of other requests that affect or are effected by the request. If your business uses other Atlassian products, this list may include linked development issues.|
|Assignee||The team member assigned to work on the request.|
|Priority||The importance of the request's resolution, usually in regards to your business needs and goals. Sometimes, priority is calculated by impact and urgency.|
|Labels||A list of extra custom labels used for categorizing or querying records.|
|Request participants||A list of extra customers who take part in the request, for example, people from other teams, or vendors. Read more about participants.
|Approvers||A list of people responsible for approving the request, usually business, financial or technical contacts .|
|Organizations||A list of customer groups interested in the request's resolution.|
|Impact||The effect of the change, usually in regards to service level agreements.|
|Urgency||The time available before the business feels the request's impact.|
|Change type||The category of the change (usually standard, normal, or emergency). For example, a standard change does not require action from change managers. A normal change does.|
|Change reason||A short description or code that indicates why the reporter needs the change.|
|Change risk||The risk of implementing the change determined by the change advisory board . Usually based on complexity, scope, testing, recovery, timing, etc.
|Change start date||The scheduled date the change's implementation .|
|Change completion date||The date the change's implementation is complete.|
|Change advisory board (CAB)||A list of individuals responsible for assessing, approving and scheduling the change.|
|Pending reason||A short description or code that indicates why the change is not progressing.|