Service Desk changes project permissions

Hey everyone,

we've moved some of our projects from a JIRA project to a Service Desk. Problem is: Now our users which do not have a Service Desk Agent license can't track time on these projects. How can I fix that? It has to be possible for an employee to log time on an project without wasting an expensive Service Desk Agent license just for this?!?

P.S.: We use Tempo for time tracking.

Thank you in advance.



I'm currently checking the permission schemes. We have a JIRA group called "employees" which has the permission to work on an issue from a specific project (in other words: log time on in). But nonetheless our employees aren't able to log time on a project, if Service Desk is activated on that project.



Do i have to give the "employee" group the project roll "Service Desk Collaborators" in order to make them able to log time?



Could it be that the "permission scheme for Service Desk XYZ" only works for newly created issues? If that's the case, which permission scheme works with the old issues of said project?

6 answers

I have the same problem with tempo timesheet plugin

0 votes

Hi Simon,

As of right now, only Agents can edit issues, so I'm afraid you are kind of stuck here. If you'd like to check JSD permissions, please check this page:

Well but they only need to access and edit the issue from the project view, not the service desk view. Can Collaborators log time on SD issues?

Thanks for the replys.

I understand Atlassian wanting to sell as many Service Desk Agent licenses as possible. We've already bought licenses for everyone who works directly at the issues. But we simply can't afford to buy licenses for every collaborator who does a small part on solving a ticket every now and then (for example our developers) just so that he can log his time!
I've already disabled Service Desk on our projects in order to make people able to log time on them again. So basically now we're stuck with a solution we bought and licenses we bought, but we can't use them!
Also, I cant understand how Service Desk is able to prevent JIRA users from logging time via Tempo, as both are different Addons.
I've followed and voted for the suggested features you've linked but well... It's been on "to do" for 4 respectively 8 months now which means Atlassian hasn't even begun to work on that.

In other words: We're screwed.

I don't understand why Atlassian didn't sell both Service Desk license models. So everyone can choose a license model for there requirements. We are in the happy situation to be a license 1 customer.

I believe a workaround is to make a parallel non-service desk project and book time against that. Fiddly though.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

370 views 1 1
Read article

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