Adding SLAs from Service Desk to JIRA Software Project

Hi!

We have a really big and high load project using Cloud JIRA Software - with Kanban board looks like

Lenses Board - Agile Board - Looksery 2016-12-12 19-55-03.png

Now we want to add kind of SLAs to it, to track by time how tickets move through statuses.

I started JIRA Service Desk trial. Is any way to add SLAs except change time of project from Software to Service Desk? Will this action change anything except adding extra features?

After testing with changing project type I see that Request participants/Organizations are added, Comments UI is slightly changes, links to Kanban board is hidden from sidebar. We'd really prefer avoid any changes for all usual users.

Do anybody have experience to adding JIRA Service desk features to a big existing JIRA Software project? Any tips will be appreciated!

1 answer

1 vote

Hi Pavel,

JIRA Software and JIRA Service Desk are two different applications serving different goals. Without going into all the nifty details, both are built on the JIRA platform (which gives you projects, issues, versions, components, workflow and a lot of other common things), but JIRA Software essentially aims at supporting a software development process whereas JIRA Service Desk is intended for Service Management either by IT or other Service Teams.

You noticed correctly that the UI between both types of projects is different. Service Desk offers you SLA's, queues to manage issues, specific reports and automation rules. JIRA Software offers you scrum and kanban boards, integration with dev tools, a release hub and so on.

On top of that, there is also quite an important difference in licensing. You can find some more information regarding that part over here.

But in short: do not use JIRA Service Desk for a software development project. That is not what it is designed for. You could however use it complementary to JIRA Software. It is meant for your (external) customers - who are not JIRA Software Users - to report bugs and change requests. These can be linked perfectly to issues in JIRA Software, so support and development teams can work in there own dedicated, but linked environments.

Walter, thanks for comment.

It's not actually software development, it's development of content. And adding of SLA reports will help as much, as this content is required by external users. It can be easily combined with existing Kanban and everything, which is convenient for currently usage.

But providing Service Desk licenses for everybody is pretty expensive indeed... Unfortunately, JIRA forbids to transition and edit of issues for non agents, even if they have all other permissions for a project.

The part about the licensing is true. But you could take a look at the Control Chart report (this already gives you some insight in lead times on your issues). You could also search the Atlassian Marketplace for some SLA specific add-ons.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

433 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you