Hi,
We have one project which is "customer facing" that is using email as the way of creating tickets. (To also be able to have communication that person is created as a customer) so to achieve this in the Customer Permissions we have selected the "Anyone can raise a request on the customer portal or by email"
But the problem we are facing is that we have another "Service Desk" project which is internal, and there we have the permission "Customers who are added to this service project"
So here is the dilemma, how can we hide the "customer facing" project from the portal without disrupting the functionality of emailing that project?
Thank you in advance!
Best regards, Alexander Westergård
There are ways in Cloud, but not DC. If the goal is to hide the portal, you will need a marketplace app or use the workaround shared by Florian. There is an open feature request in the Atlassian public issue tracker that you can vote and add yourself as a watcher to receive notifications.
I'm not sure there is a way to do this. You can at least remove the request type from any group, so the portal will be empty and user will no create tickets in the wrong portal.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No it do not impact email request. It remove it from the portal view only, you can keep use it as email request type or rest api.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.