With JIRA Service Desk v2.2-OD-08-D20141208... when "Service Desk Customer - Portal Access" has permission "Browse Projects" (the default), a service desk customer can see all portals, via servicedesk/customer/portals
I only want them to see the specific portal for which they are a user.
If I remove "Service Desk Customer - Portal Access" from that permission, a customer is unable to access the portal corresponding to that project.
If I then add "Project Role (Service Desk Customers)" to that permission, the customer does then see only corresponding projects, which is good (though surprising, since it suggests the role rather than the permission, is being tested by servicedesk/customer/portals).
However, service desk now reports the following Permission scheme error
(Is it safe to ignore that?)
Also, with either of those permissions I'd expect the customer to be able to browse issues in the corresponding JIRA project (ie via /browse/PROJ), but that URL redirects back to the portal (as does /browse/PROJ-2 etc).
In summary, how can I configure things so that:
References to relevant issues in https://jira.atlassian.com/browse/JSD would be appreciated.
I think I've found the answer to the first half of this question:- on the portal > people > customers page, make sure you have the "restricted access" button (as opposed to "everyone can access").
Now, how do I give customers access to browse JIRA?
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
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