I've granted a user Administrator and Scrum Master roles in the People section in Project Settings on a Jira project. This person cannot create a new sprint. I thought granting permissions in the People section permission declaration over rode what is in the permission scheme?
Turns out its a confirmed bug:
The people section works with the permissions, it's not an "override".
Permissions are a set of rules that say who can do what. Create issue, edit issue, transition issue, work with sprints, set assignee etc - all actions that can be allowed to accounts. The accounts they are given to are variable and dynamic - you can name a single person individually if you want, but you can also grant permissions to issue-roles like "assignee" or "reporter", fields, or, groups and/or project-roles.
If you grant a permission to a group or a role, then anyone in the named group, or in the named role in that project, gets the permission.
The "people" section is where you put people into roles.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Mark Sedlacek
In the People section of Project Settings you are assigning the user to Roles in the project. That section by itself does not grant any permissions to a user.
The user's permissions will be granted based on the Roles to which they are assigned, and the permissions granted to those Roles as detailed in the Permissions Scheme.
The Permissions Scheme is the authority on the permissions allocated to users/roles for the Project.
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.