We're opening up Jira access to our service desk project to some of our clients, to give them more functionality than they can get via the web portal (e.g. view attachments).
We've got issue security configured so that they can only see the issues we want them to, but whilst testing I've noticed that they can also see the Service Desk config tab with:
We don't want them to be able to see this information (e.g. and see that they have different SLAs to other clients!) and it's bizarre that they are able to.
I've been through the roles and permissions, and can't see any way to restrict this.
Am I missing something or is there no way to hide the service desk config from users who have the "Service Desk Customers role?
The customers are only a member of the Service Desk Customers Group
In addition, the project's permission scheme gives them the following (so that they can log into Jira directly)
I can't see why any of these permissions should allow them to see the SLA configuration, queues, etc. In my view the "Service Desk" menu should be hidden entirely from customers.
In the meantime I was also answering a similar question in another thread:
Basically if you open-up your JIRA instance the minimum permission that customers need to view projects is the Browse Project permission. This permission also gives users the ability to watch Service Desk metrics (SLA, Reports,...).
Uptil now I haven't found a way to pass this behavior.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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!
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