I created a user and want to configure his permissions in a way that he can only have access to 2 of the projects that we manage in Jira. How can I achieve this?
I tried to read several articles I found online but got lost.
This all depends on the permission schemes that are configured for those two projects - they may have a shared permission scheme, but they also might have different permissions.
This also depends on the type of access the user should have to the projects - should he or she have full access? Read-only access? Project admin access?
If you can figure out the type of access you want to provide this user, then take a look at the permission schemes for these projects, you can then figure out how you will need to add the user to the project. As mentioned here, project permissions are granted based on:
Hope that simplifies it a bit for you into actionable steps. Every JIRA instance handles this a different way, so I can't really give a straightforward answer since I don't know how that JIRA instance is set up.
I would not put him in the admin group you mentioned as he would be able to see the same thing you do.
If you want to give him admin permissions for those two projects and you're using the default permission scheme, then you should just be able to add him to the Adminstrators project role just for those two projects (the project role is not the same thing as the admin group you mentioned).
Sounds like this user does not have the "Browse Projects" permission under the current permission scheme. If you're using the default permission scheme, this permission is granted to the Users project role, so you'll probably need to add him to that project role, too.
Re: the JIRA Software checkbox - is the project a Software project? If yes, you will need to check this box.
What groups do you have configured in for the JIRA Software Application Access? You can find that in the admin under Applications > Application Access.
You should see a list of groups here - what is the default user group set under Application Access? If that group has permission to see everything, then he is also going to see everything.
At this point, I would look at the user's project roles in the User Management section in the JIRA admin. Find the user in User Management, then in the Actions column, click the option to "View project roles" - here, you'll be able to see which projects the new user has access to and why (whether he has been added to a project role directly, or if he is part of some user group that belongs to a project role).
My current guess as to what happened here is that the jira-users group has access to all projects and the new user was put into that group automatically when he was added to the JIRA Software application.
It isn't good practice to add the jira-users group to ANY permission scheme or role unless you specifically want EVERYONE to have that permission. Using it in permission schemes causes this problem to many people. I've had very few projects I've ever wanted universal access to
Click on Permissions next to "Copy" and "Edit" to see a list of various permissions and which users/roles/groups are assigned to each permission.
You can add/remove users/roles/groups to these permissions. Any changes you make to the scheme(s) will be reflected on the projects which use those schemes.
I think it is finally working the way we wanted now.
What did I do?
• Used a different permission scheme for the 2 projects we wanted to grant him access. Everything else remained on the default scheme.
On the default scheme:
• Changed the permision to Browse Projects from "Application Access: Any logged in user" and changed it to "Group: Develoment Team" (I created this group with all the employees on it beforehand but Mark)
On the new scheme:
• Under Administer Projects: I granted him permission using the single user option.
• Under Browse Projects: Removed "Application access: Any logged in user" and changed it to "Group: Development Team" (I created this group with all the employees on it beforehand) and added him using the single user option.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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