Our organization uses various JIRA projects but there is one that I need to open up to an outside person. I only want that person to have access to one of our projects but he can currently see all projects.
The majority of our projects use the default permission scheme which allows the users group. If this user is removed from users he can not login or access anything. So I need to allow the user to login to JIRA OnDemand and only access the one project.
It can be performed in different ways but the one with the least changes would be to:
1. Create a new group and add the user there
2. Add the group to the Global Permissions (Jira Users) so the user can log in
3. Remove the user from the group 'users' that is enabling him to see all the other projects
4. Add the new group to your project's Role (Users) to grant him access to that project
We have the same issue. We have added a user with only one group present. We added that group to the proejct we want him to have access. When we test this setup the users sees all the projects we have. Our setup looks correct and this seems to be a bug. We need help in resolving this issue.
Most likely your permission scheme still has Any logged-in user for the Browse projects permission.
I wrote a very detailed, step-by-step article on how to fix this. Please have a look:
We do not have any permission sheme that consist "Any logged-in user". I am sorry to report but something is wrong with our account. We have tried everything and the setup is correct. We have followed you instructions, setup everything from the beginning and still the same issue persists.
1. We have setup a group called: users-actie
2. We have created a user called: Tester09
3. We added Tester09 to group users-actie
4. Tester09 is not part of any other group
5. We added group users-actie only to the given project
Still when Tester09 logins it sees ALL projects. We cannot change this behavior and we need this to work ASAP.
Please advise. Please take a look our account and insure that eg. Tester09 can only see project he is assigned to and not ALL.
Hi Mauro, I have followed your instruction and it worked so far. But now when this user creates an Issue in the Project Field he can see the titles of all other projects which is not good. Is there a way I can prohibit that, or did I miss something in your instruction?
The key thing that threw me were the project permission scheme 'Default software scheme' which is setup by default when you choose 'Kanban' projects. This permission scheme basically give permissions to everyone to everything... Changing it to 'Default Permission Scheme' solves this, making it only available to Users defined in the Project's 'Users & Roles'
Thanks for the video, one question I had was if we remove "Any Logged in User" from he Default Software Scheme. Wouldn't this effectively restrict access to view projects and tickets within them to users associated with that particular project? Right now we have access to all projects and I don't think we want to restrict that.
I have created a step-by-step guide for the new Jira interface as an answer to the question here:
If you need any help on this, I've just created a new KB with a step-by-step guide and a video to better illustrate them, so I'd recommend you check it out!
Let me know what you think!
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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