I have a client with a group of users who I want to restrict to only one project in JIRA - I don't want that client group to see any of my other projects. I've been through the documentation and cannot work it out.
You should create a different project permission scheme for the project and add this group of users only to this permission scheme. In this case the group users will only be able to work with the single project.
I sounds, like many administrators, you've taken the default from Atlassian of allowing the default logon group, which every user is put in upon creation, (jira-users or similar) permission to everything. JIRA doesn't allow RESTRICTING access. It works on the best practices of GRANTING access to ONLY those things needed. For @Alexey Matveevs answer to work you'll need to either:
1. remove the users in question from the default logon group, create a new logon group, and put that group in the permission scheme for the new project. The downside is unless JIRA changed every new user will be put in BOTH the logon groups.
2. This solution will be a more time consuming depending on your setup. Convert to using project roles. This allows the project lead to add/remove users from their project. Remove all groups from the permission scheme and give project roles the permissions. As your system grows there will probably be more projects you want to limit access to and you'll easily be able to do it.
I have a similar problem - but I feel like I've done as everyone has been suggesting and still can't solve it.
I've created a 'restricted' Permission Scheme, and added several projects to this. In the "browse projects" permission, I've added a single group. I do not belong to this group.
When I view "all projects", I can still see all of these projects that are supposedly using this 'restricted' permission scheme. I can't open these projects, but my understanding is that I shouldn't even be able to know they exist.
I do not have 'Jira-users' in my setup - meaning, I haven't granted any permissions to 'Jira users' except for in 'Application Access'.
Project roles are empty, we have not used this feature and there are no defaults set here.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs