We have a Jira instance running in our internal network to make it possible for teams outside our organisation to use this instance, we have Jira accessible via a loadbalance as well. However, when setting up service desk, which is purely to be used for internal ticketing, we want to disable access to Portal through Jira's public URL and only have it available internally. Is there any easy way within service desk configuration to do this?
Why not just restrict access to that Service Desk project?
Hi @vatsal_dhar,
there isn't a setting to make the portal available from a different URL than the Jira where it is installed. If you want to have only internal access, you will need to play with your firewall/proxy rules to restrict the URLs used by the Service Desk portal but without any guarantee that it will not break something.
The best practice would be to have two separate instances: one public and one private.
This is what is recommended by Atlassian, using Federated Instances so that both Jira can communicate, link tickets between the two, etc: https://confluence.atlassian.com/enterprise/federating-jira-managing-multiple-instances-461504624.html
Let me know if that helps,
--Alexis
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.