{"id":3959,"date":"2021-07-08T17:04:23","date_gmt":"2021-07-08T15:04:23","guid":{"rendered":"https:\/\/devsite.almarise.com\/?page_id=3959"},"modified":"2024-06-27T10:21:26","modified_gmt":"2024-06-27T08:21:26","slug":"service-desk-problem-management-integration","status":"publish","type":"page","link":"https:\/\/devsite.almarise.com\/en\/case-studies\/service-desk-problem-management-integration\/","title":{"rendered":"Building a Workflow and Process for Service Desk and Problem Management Integration"},"content":{"rendered":"

Jira Service Management Case Study<\/h2><\/h2><\/div>

Building a Workflow and Process for Service Desk and Problem Management Integration<\/h3><\/h3><\/div>

Good Incident Management in Organization is not an easy thing to accomplish. To make it more obvious, let\u2019s start with the definitions.<\/p>\n

An Incident is an event, which makes a service work in an incorrect way, not included in the specification. A Problem \u2013 on the other hand \u2013 is the underlying cause of an Incident.<\/p>\n

No one is happy when an incident occurs. Often, the root problems are too complex to be resolved by the 1st Line of Support in a Service Desk project. The underlying issues usually lie deeper in the system and require a higher level of expertise to address effectively. This complexity means involving more specialized teams who can thoroughly investigate and resolve the fundamental causes of the incident. The process might also include the owner of the service and the management. All these people will need to cooperate at some point. As you can see, this is a complex situation.<\/strong> Thankfully, this can be managed.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

The Solution<\/h2><\/h2><\/div>

We\u2019ve created a solution to this situation, basing it on the principles of ITIL good practices. The solution assumes dividing and synchronizing the scope of work between the Service Desk and Problem Management projects. Both projects need to be able to communicate both with Service Desk and the requestor.<\/p>\n<\/div>

The Requirements<\/h3><\/h3><\/div>
    \n
  • Creating a second Software or Core project meant for the people not requiring a Service Desk Agent license, e.g. software developers or managers.<\/li>\n
  • Automatic solution copying issues classified as a problem to the Problem Management project. The issues will be linked by a Jira link as an Incident and Problem (from the respective sides).<\/li>\n
  • Automatic synchronization script copying comments between projects, so both the issues have the same information regarding the work process.<\/li>\n
  • A possibility to close the Incident by applying a workaround, if the requestor agrees.<\/li>\n
  • A possibility to turn on the public comments function for users without a Service Desk Agent license.<\/li>\n
  • Synchronization of statuses allows the requestor to see what\u2019s going on with his request.<\/li>\n
  • Acceptance and Analysis process.<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
    \"Service<\/span><\/div><\/div><\/div><\/div><\/div>

    The Workflow in Jira Service Management<\/h2><\/h2><\/div>

    Below you\u2019ll find the workflow which was created for the sake of our solution in Jira Service Management.<\/p>\n

    <\/div>\n<\/div>
    \"Service<\/span><\/div><\/div><\/div><\/div><\/div>

    The Benefits<\/h2><\/h2><\/div>

    Our solution primarily allows us to save the employees\u2019 time by integrating Incident and Problem management into one, transparent process. The desirable side effect is saving the license cost for Jira Service Desk licenses.<\/p>\n

    It also allows us to transparently present the work progress to the requestor and shift the responsibility from Service Desk Agents to a qualified Platform Support team.<\/p>\n

    <\/div>\n<\/div><\/div><\/div><\/div><\/div>

    Contact us!<\/strong><\/h2><\/div>

    Got any questions? Contact us. We\u2019ll get back to you within a maximum of 1 business day.<\/p>\n<\/div>