Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage


I know how to make a Software Project public (, but this generate an error (attached) when applying to a Service Desk Project. Any workaround?




2 answers

Thanks for the suggestion Colin. But we're working on a cloud instance, and from what I've seen the plugin is only for servers.

0 votes

The permission for Anyone group is not supported by Service Desk. This is because in JIRA Service desk we have JIRA access (Agent, Admin) and Portal access (Customer). Granting the Browse Project permission to the Anyone group means that anyone can access the project and view all the issues in it. This will cause certain functionality of  JIRA Service Desk to be disabled.


If you are looking to give access to all the ticket, you can group user by Organization and share the issues with Organization.

Thanks for the feedback, Amirul. I have a couple of questions:

- Which functionality exactly would be disabled if I allowed the "Anyone" group to browse the project? (Maybe I can live with it)

- By grouping customers in an Organisation and adding this organisation by default to all my tickets, the customers still need to be registered and logged in to be able to browse through tickets, correct? If that's the case, I could just enforce registration for customers, and then grant access to the Customer - Portal access only to browse the service desk project, right? My point is that customers still need to register in the first place, which I was trying to avoid.

FYI, we are trying to set up a transparent issue queue for an open source initiative, so ideally, all issues should be visible in read-only to customers.

Keen to know how to handle this kind of situations

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

241 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you