Using JIRA Service Desk for SLA only : the tutorial


Posted by
Anand UNADKAT

August 11, 2014

The name of the product speaks for itself : JIRA Service Desk is designed for Service Desk applications of JIRA. And it comes bundled with a lot of features : queues, SLAs, reports, permissions etc. But if you are working in one of these companies which only need to track SLAs – whatever the use case you are working on – that’s a lot of clutter to deal with.

The good news is you can tune JIRA Service Desk to suit your need. Yes, you can have just the plain, old, back in the days VertygoSLA features that are now integrated in JSD. Let me show you how.

JIRA Service Desk simply for SLA

From a customer perspective, this looks like a tricky scenario. In fact, it’s pretty simple : you only need to know that you can disable any unnecessary features from JSD. Indeed, all the features that JSD has to offer are built as ‘modules’.

If you are a developer, you could build the modules you need yourself and test them using Atlassian SDK, as these are additional functionalities that you would want from JIRA, but let’s not get ahead of ourselves. 😉

The current version of the add-on (1.2.6.1) has 164 modules that are enabled by default when you initially installed the add-on. These modules can be disabled i.e. removed from users view so they feel they are using standard JIRA version. The solution I will show you consist in disabling each feature one by one, so you are only left with SLA.

This requires JIRA Administrator permission.

Disabling unnecessary modules

Go to: Administration > Manage add-ons > JIRA Service Desk > click on ‘164 of 164 modules enabled

1. Disable ‘Create Issue’ drop down functionality to ‘Create Service Desk Request

1

Module to disable here is called ‘create issue-replacement’ . You will then get :

1-1

2. Disable ‘Service Desk’ section. This is the one next to either ‘Agile’ or ‘Issues’ menu on the top, depending on the version of JIRA you are using.

Module to disable here is called ‘service desk-section’. The Service Desk section disapears.

2-2

3. Now let’s tune the project section.

3

Disable ‘People’ section from Service Desk Project

This is to manage permissions on who can manage SLA’s, reports etc, but if you use standard JIRA permission scheme then you can assign it to this project, which eliminates the usage of this function within JSD

Module to disable here is called ‘agent-people

4. Disable ‘Customer Portal’. This is the view that the customers will have when raising a Service Desk ticket, if you are not using this feature, then you don’t need this either. This section is for creating request types that customers can raise.

Module to disable here is called ‘agent-customer-admin

5. Next is to disable reporting. Reporting is quite limited, as it will always give you a graph. You can choose to use reports offered by JSD or, you can use JIRA dashboards, in which case you can disable this too.

Module to disable here is called ‘agent-report

6. Disable queues. If you are using standard JIRA project, then you don’t need queues either as you can use dashboards to view your queues.

Module to disable here is called ‘agent-queues’ . Here is the final result :

6-6

Only downside here is, since JSD home page is queues be default, you will be taken there straight away. It is just disabled from the view, but it is still active. So you will still see the queues section, however you can delete all the default ones.

Just a SLA section, finally!

Now you are left with just the SLA section. You don’t have any view of Service Desk, so how do you go to the SLA section? Simply by going to Projects > select your project > Administration > Service Desk > SLA

I find this tricks quite cool, because the result is seamless for end users. It feels like they are using standard JIRA functionalities, but actually they are using JSD as well. It’s just hidden from users view.

Now you’ve got a way to take full advantage of the SLA feature while keeping your usual JIRA interface.

If you haven’t tried JIRA Service Desk yet, maybe it’s time to discover it :

  • Anand Unadkat

    Hi Oskar,

    This guide is for version 1.2.6.1. However I would assume most of the modules still remain the same.

    Regards
    Anand

  • Is this guide still up to date?

  • Anand Unadkat

    Hi Matt,
    I totally understand what you are trying to say :) The reason why I had this blog is because I have had clients who are prepared to pay for the plugin and don’t want to use any other feature apart from SLA, because they simply want to track the SLA and anything else become a pain to maintain.

    It is a funny one I know, but you will be surprised how many people like going this route :)

    Thanks for your input! I’m glad you found it useful!

  • This is useful information but it’s pretty funny though. Last year I could buy the SLA plugin. Now I can pay more for Service Desk to get the same SLA features (and a lot more, I know). Then I can use this blog to remove everything from Service Desk that isn’t the SLA plugin.