I have a pretty simple request and have discovered many conflicting answers on the forum and the internet.
How do I restrict access to a group of users to a single project? They should have the ability to work on tickets but not administrator our project.
I don't think you've found many conflicting answers, just a lot of discussion about people assuming it should be done in one way that it is not, and a lot of stuff about having to fix up the defaults Jira ships with.
In theory, it is very simple. You create a user, add them to a group that lets them log in, and then add them to a role in the project that lets them see the project (or group if you're doing it that way). You don't add them to other projects, then they won't see them.
It really is that simple.
But what causes the problem is that the default setup in Jira is to create projects with that "can log in" group set to allow access to the project. So every project you create gets everyone access to it.
That has to be unpicked before you can do "one user who can only see one project"
Your comment of 'They should have the ability to work on tickets but not administrator our project. ' indicates you're giving project administration access of everyone. Is that the case? If so you should stop. You'll have all kinds of stuff happening with no way to track who changed what. I've been at places were people were given more authority than they should have been and some people just start 'playing around' to see what happens if they do 'this'.
@Nic Brough -Adaptavist- is right; get rid of the JIRA default of allowing everyone who can logon access to everything and assign users just what they need. Most the seasoned users use project roles because it allows you to fine tune permissions and workflow conditions. It allows you to have one permission scheme for all projects and the project admin administers the membership in the roles to the user they want to have them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
What do you mean by access? Do you mean browse issues? If so, then you should grant this group of users only the Browse Issues permission in this project. Make sure that the permission scheme, which you use for the project, is not shared with other projects.
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.