When companies adopt these practices, they give support engineers and analysts a detailed understanding of how the ITSM structure works, making service delivery efficient rather than leaving them wondering: “What’s the difference between an incident and a request?”
Once a basic understanding of ITIL for ITSM has been grasped, any service desk or IT manager with application administration skills can implement this framework in their help desk solution. This is where Jira Service Management comes in - to champion those ITIL requirements the business has.
I rolled this out internally at Clearvision. Read on to see how I achieved it…
Jira was already an established application across multiple teams here at Clearvision, which is often the case in many companies that demand Jira Software as a development tool. IT support issues were logged, tracked and recorded via a Jira project.
This, understandably, had its limitations, which is why we made the collaborative decision to add and configure Jira Service Management for our IT team.
How we introduced ITIL framework
One of the most commonly adopted best practice frameworks for ITSM is ITIL, which is why Atlassian has ensured that Jira Service Management is ITIL-certified in the four core processes from PinkVerify™ and Axelos™.
- Service requests
- Incident management
- Problem management
- Change management
We made use of Atlassian’s ‘Best practices for IT teams using Jira Service Management‘ knowledge base as a guide to get us started with ITIL processes, and used our own experience to mature our Service Desk.
Any business, small or large, will experience:
- Unplanned maintenance,
- Outages
- Problems
- Requests for changes
These all require an incident/request/change/problem to be logged and managed by a member of the IT team. We implemented the best practices outlined below to help us on our way to creating a Service Desk fit for our organisation.
Jira Service Management Best Practices
Change Management
Those of you familiar with change management processes know that it involves planning, control and business impact research. This can all be integrated into your Jira Service Management with the following guidelines:
- Have a separate “change” issue type
- Create and configure a workflow that meets requirements for reviewing, planning, approval and implementation. See below:
- The workflow can then be amended to include additional requirements your business has
- Enforce an approval step for change reviews – many enterprise businesses have a dedicated Change Advisory Board for this purpose (CAB)
- Coordinate changes with a calendar – we recommend Confluence Team Calendars, as they can be used to ensure this is a fluid process
- Default form fields for change requests – create issue type fields and screens for your change requests, including change type, change risk, change dates, impact, urgency, etc.
Incident Management
Start with the best practice guidelines below to optimise your incident management with Jira Service Management.
- Start with an “incident” issue type in your Service Desk Project
- Create and configure a workflow – see the example below:
- The workflow can then be amended to include additional requirements your business has
- Auto-close incidents after resolving them
- Link incident records to other issues
- Default form fields for incident reports
Request Fulfilment
Likewise, Jira Service Management also allows you to optimise your service request fulfilment in the following ways:
- Create a separate “request” issue type
- Create and configure a workflow that meets business requirements – for example:
- Incorporate your approval process into the workflow
- Auto-close service requests after resolving them
- Default form fields for service requests
Problem Management
When your users run into a problem, Jira Service Management’s integration with Confluence is an excellent way to allow them to search your knowledge base for answers. It allows for quick, simple problem management:
- Create a “problem” issue type
- Create and configure a workflow that meets business requirements – for example:
- Document known errors in your linked Confluence knowledge base on an ongoing basis
- Default form fields for problem reports
More Jira Service Management Tips
In addition to the guidance on the above four processes, there are plenty more Jira Service Management offers that help agents and customers. Here are some more great Jira Service Management tips to finish up with!
Keep your agent queues organized
Ensuring your queues are organised for your team creates a more efficient and user-friendly experience. For example, you can create a triage for new issues, separate incidents, problems, requests and changes, and add a queue for approaching SLAs.
Don’t over-complicate your portal
Keep your request types to a minimum. You don’t want users to be baffled by too many choices. You should always ensure the most common request types are covered, but keep it as simple as possible.
Use canned response templates
Who would want to type the same comment over and over? With canned responses for JIRA, you can create templates to send responses to your customers.
Create automation rules
Automation rules in a Service Desk can be a godsend. Here are the automations we use here at Clearvision daily:
- Automatically transition an issue based on comment type
- Re-open issues on customer comment
- Provide an auto-response acknowledgement
- SLA alerts
- Urgency/impact matrix custom rule for automating priority
For my team and me, Jira Service Management has had a hugely positive impact on how we deal with IT issues. Implementing and using Jira Service Management has been a beneficial experience which keeps growing every day, as we continue to improve and adapt to our business and users’ IT requirements. I hope you’ve also gained some tips on how to improve and adapt your own Service Desk environment from this blog post!
For information on ITSM and Jira Service Management, and how to get the most out of your help desk environment, contact Clearvision about our ITSM solutions today.
Published: Jul 5, 2018
Updated: Jun 28, 2023