Hey @Kate Alexandrov,
for this to happen you must make sure, that all other projects are not accessible for these users, let's call them jira-externals. The others need to be able to access all projects, let's call them jira-internal. In order to remain as flexible as possible without getting entangled with strange permission schemes, it is recommended to grant access to your projects using roles instead of groups.
Therefore, in any group that you want to hide, make sure that the Browse Projects permission is only given to users who are in a certain role of your project (for example the project role users). Then you can use this role to determine, who has access.
You can also give this permission to multiple roles (for example admins, developers and users), this way you don't have to add a person into three roles to give them admin, development and user permissions. But this is a bit more advanced, so don't worry too much about it.
Okay, so to put my explanation in a correct order, here are the steps you can take:
- Add your users to a group, that let's you destinguish who belongs to which. → Following this example, I would create the groups jira-externals and jira-internals.
- Add the group jira-internals to the project role users in every project.
- For the Project Role Settings, set jira-internals to be a standard that will be added to every new project.
- For the project where externals gain view permissions, add them to the project role users
- Modify the Permission scheme (Let's pray that you have a shared one for each project), so that the Browse Projects Permission is only granted to People who belong to the Project Role Users, Developers or Administrators.
That's it, now you should be all set up. I hope this was what you are looking for.
Cheers,
Andrej from greenique.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.