We are setting up the service desk portal for a customer of ours.
We do not want to give them access to Dashboards within the project nor to be able to use the create function from the project page also. The reason for this is to be able to lock them down to purely using the portal.
Unfortunately this means they are unable to also view tickets raised within that project by anyone else. It also means that for some really strange reason, when they use the search function to find even their own tickets, they cannot find them, they have to use keywords which seems a little silly.
How do we set it up so that they can search using the issue number from the portal and also be able to search / view all tickets raised in that project from the portal?
I have had to give them Browse Project access via the Service Desk Customer role.
Down side to this is that they are now considered as a support group and can only post internal comments meaning we cannot use the internal comments to ourselves.
Ideally the Service Desk function should allow you the ability to set permissions in a more detailed way, the same goes with the Projects. But I have found this tool to be very limited when it comes to a true Service Desk offering. It is fantastic for developers to manage projects, use Agile etc but that's where it ends unfortunately. I have ended up just giving the customer access to the project and bypassed the portal all together because it is far more hassle than its worth. The fact you cannot search for the issue number in the portal itself really just proves how far away they are with this product in comparison to something like Service Now or even HP and Zen Desk.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot