You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I know this has been asked several times in the past, however I still cannot discern a clear answer. Either that or the answers I have found don't apply to the current state of JSM.
I have a service desk in which customers can sign up for an account on their own and fill out a request. I do not want this public.
I want to open a second service desk that is public where an account/sign-up is not needed.
This doesn't seem possible as the setting for making the portal public is a global one and not a project level setting. Either that or I am not understanding how to accomplish this.
I did think about a completely new cloud instance, but that's less than ideal.
Can anyone offer me insight?
Hi @jfischer
You are correct, the portal for JSM is a combined portal of all JSM projects you have created in your instance. There's no out-of-the-box option to make requests from one project public, but not another.
You might be able to accomplish this with Refined for Jira which lets you customize the access for different 'sites' within JSM, I'm not sure it will let you have one public and one not though. I don't know if adding an add-on is more ideal for you than spinning up a second cloud site, but if your license count is 10 or under the app is free.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.