My team would like to have the ability to have one user, A, be a lead developer on project X, for example. However, we want user A to not be a lead developer and be a regular developer on project Y. We want the user to have different permissions (closing issues, etc.) on the two projects. Would I simply use a project role for this? I'm trying to figure out what the difference is between a user group and a project role. I understand the role is project specific but the user group is global, but I don't see how a user group would be helpful for us for these kinds of situations.
Let me try to help using these points.
I hope I didn't confuse you further.
I think for our usage maybe we'd want to be assigning certain users to permission schemes rather than using project roles, correct?
For example, if we have 3 users in a Lead Developer project role, but then in a permission scheme allow the Lead Developer to close issues, that means any of those 3 users would be able to close the issue even if they aren't actually a lead for a project. Correct?
Project roles are project specific. In project A you make the user a lead developer. Their role in project A has NO effect on their permission in any other project. The long standing security model says you never give individual users access to resources. You give a role or group access to the resource and put individual users in the role or group. In most cases you have many more resources than roles or groups so if a user leaves it is safer, from a security standpoint, to remove them from roles or groups than trying to find all the resources they have access to and remove them from those.
You can use user roles to do that. I don't like groups for a three reasons. 1. They require the JIRA admin to administer the membership, 2. They often don't give the desired level of control, and 3. Roles allow the project admin to manage the project users. Most old timers don't use groups for those reasons. The other advantage you can have one permission scheme for all projects when you use roles.
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