Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How can I switch from private to public jira project?

Melody Strauss February 1, 2018

I have a project that was initiated as a private project and now I am ready to put it into production so I want to make it public but I can't see how to do it.

1 answer

1 accepted

2 votes
Answer accepted
Thomas B
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 2, 2018

I would assume that your Project is using some sort of Permission that is restricting access to any users that are not associated with the Project Permissions. To change this, you can either modify the existing Permissions or create a new Permissions Scheme. I would recommend the second option. 

Recommended:

  1. Go to Admin Settings > Issues > Permission Schemes
  2. Click Add permission scheme and give it a Name
  3. Once this is complete, under the actions tab, click Permissions
  4. Here, you can assign groups to any given Project Permissions (I'd recommend creating a group of users for visibility)
  5. Once permissions are set, go back to the project and associate the new Permission Scheme with the Project
  6. To do this go to Project Settings > Permissions > Actions and select Use a different scheme
  7. The project should now be visible to all users

Alternative

  1. Go to Project Settings > Permissions > Edit permissions and repeat step 4 above
  2. The only reason I don't recommend this way, is because all other projects associated with this Permission Scheme may inherit the new permissions. 

 

Hope you find this helpful.

Curt Timmer May 21, 2019

I've done these steps and I'm still struggling with getting the external users to have access to the project.  No matter what Atlassian url they hit, they are automatically routed back to our servicedesk url.   or I get the message saying that don't have access.

Here's the steps I took.

1. copied default project permission scheme, named it Customer Facing Permission Scheme.

2. Changed project to use new permission scheme

3. created a new project role called Customer Ready Only.

4. added customer, assigned new role to customer.

5. updated the Customer Facing Permission Scheme and granted the project role of "Customer Ready Only" to Browse Project

 

Still can't get it to work.  Ideas on what I'm missing, it's probably something real simple?

Ryan Gillespie
Contributor
May 31, 2019

Actually having that same problem concept right now Curtis. I gave a user a link to an issue in QA (we are just starting with opening up our projects) in a software project and when they click it, zip, back to the service desk portal they go.

Edit: I believe I just solved it. Under the permission scheme:

1. Grant Permission

2. Select Browse Projects for the permission

3. Click on the Group radio button, and leave it at 'Anyone' (do not select another group)

4. Click Grant

Voila!

Like # people like this

Suggest an answer

Log in or Sign up to answer