Sidehistorik
I am in general fond of JIRA Scemes Schemes - but not (always) the Permission Schemes, because in general permissions vary pretty much - even for quite similar projects.; as similar projects often has a different set of users (and hence: permissions)
So I tend to extend the JIRA Roles pretty much in an (almost) 1:1 relation between JIRA Permissions and Roles.
...
Look more or less like this:
Create Roles for Standard Permissions
For these permissions, I create a Role for each permission in the Permission Scheme - sometimes with a little more descriptive name prefixed with "can":
| JIRA Permission | Rolename |
|---|---|
| Browse Project |
| View Development Tools |
| Assignable User | AssignableUsers |
| Assign Issues | CanAssignIssues |
| Close Issues | CanCloseIssues |
| CreateIssues | CanCreateIssues |
| ... |
| ... |
| ... |
| Move Issue | CanMoveIssues |
Create a New Rolebased Permission Scheme
Create a "Rolebased Permission Scheme", and Add the Roles to the equivalent permission:
| Tip |
|---|
You can always include users,groups and others in the Permissions, if these ALWAYS should have that access, eg: Add the "jira-administrators" group to the "Administer Projects" permission Add the "Project Lead" to the "Browse Project","Assign Issues" etc etc to the "Browse project" permission Add the "Current Assignee" and the "Reporter" to the "Edit Issues" permission |
Until all (that You want) is added in the 1:1 relation:
Assign the Scheme to a Project
...
- Overview / resolving of permission issues easier
- Changing permissions for one project very easy/fast
- Differentiating permissions on otherwise similar projects
- You only have one (or few) Permission Schemes