You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi everyone,
One of our clients told us he can, besides his, see another project (Project B). He is only a member of jira-users group.
We checked Project B's 'Users and roles' settings and under Users section was just listed 'users' group - not jira-users group. We removed even 'users' group from the project - now it has only Administrators, Addons and Developers section - but he can still see Project B.
We checked with our other client's users (only jira-users group members) and all of them can see Project B. Furthermore, if we create a new project, they all automatically see it. And we can't find a way to prevent client's users from seeing those projects. And we can't remove them from those projects since they are not added to them. Any help?
There is no issue with our other projects - clients that are not explicitly added to those projects, can not see them. The only difference we can think of between Project B and all our other projects is that Project B is the newest project - created around January 2016. Since Project B is our newest project and all newly created projects also have this issue, was some default option added to new projects around January that could cause this issue?
Thanks!
When creating a new JIRA project you are able to select a permissions scheme. If you use the JIRA Default permission scheme, this could be pretty open to all projects. If you need to limit this, new more restrictive permission schemes outlining who can do what can be created, and later applied to individual projects to limit what users see what. Check this out for more information: https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html
Thanks Jonas!
Yes, that was the issue. Our old projects have 'Default Permission Scheme' which was OK. But Project B and all newly created projects had a new default scheme 'Default software scheme' which is *very* open - it allowed every logged user to browse the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi how can i change an existing project to that project view only? Speaking of removing from the default ones like 'Default Permission Scheme' and 'Default software scheme' and add to a new created permission scheme?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.