It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Members of jira-users group can see all newly created projects and can't be removed

Ivan Qualia Oct 19, 2016

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!

1 answer

1 accepted

1 vote
Answer accepted
Jonas Andersson Oct 19, 2016

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

Ivan Qualia Oct 20, 2016

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.

 

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

682 views 7 0
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you