How to restrict access to a single next gen project

Question

We are working with external partners on a single jira project but we are having trouble restricting access to a single project. The existing documentation is for old projects and fail for next gen.

Here are the steps I tried.

1. Add users to jira

2. Remove jira-software-users (since otherwise they got access to all our projects) group for these users.

3. Go to project settings

4. Add these users by "add users/group" flow.

They are not able to see this project or any issues inside.

Jonathan Vu_qo1e0w · Answer

My team figured out a solution. We had to set all next-gen projects to private, and only provide access to the folks who need to be on the project.

Jonathan Vu_qo1e0w · Answer

I don't have an answer to this, however, I am looking for a solution to the same situation.

We have an external guest we need to invite to a single next-gen JIRA project. We invited them to our JIRA instance as a restricted user, and have added them as a "member" role on the project we need to provide them access to. However, the user is getting the same error message as Joe Hankin in the above post, "Something's gone wrong" and cannot see anything.

If this has been figured out, please let me know the solution. Thanks.

Joe Hankin · Answer

Hi Ollie,

Thank you for coming back to me. Yes, I have done both of these.

I am logged in as the other user (the resticted user), and can view the tickets when I go to Issues and filters > All Issues. But when I try and go directly to the board or view Browse Projects I get an error saying "Something's gone wrong" and can see nothing.

Should I be giving the user some form of rights rather than none at all and assume everything they need will be inheritied by the project?