As you have seen, global permissions are rather coarse in what they control and are applied globally. Since they can only be applied to groups, they are rather inflexible when it comes to deciding whom to grant permissions to.
To provide a more flexible way of managing and designing permissions, Jira allows you to manage permissions on a project level, which allows each project to have its own distinctive permission settings. Furthermore, permissions can be assigned to one of the following:
- Application access: This is for any user that has been granted access to the application
- Reporter: This is the user who submitted the issue
- Group: These are all users that belong to the specified group
- Single user: This is any user in Jira
- Project lead: This is the lead of the project
- Current assignee: This is the user currently assigned to the issue
- User custom field value: This user is specified in a custom field of the type User Custom Field
- Project role: These are all users that belong to the specified role
- Group custom field value: These are users within the specified group in a Group Custom Field
The list of permissions is also more fine-grained and designed more around controlling permissions on a project level. The only catch to this is that the list is final, and you cannot add new custom permission types:
| Project permissions | Description |
| Administer Project |
This is the permission to administer a project. Users with this permission are referred to as project administrators. Users with this permission are able to edit the project role membership, components, versions, and general project details, such as the name and description. Checking the Extended project administration option will allow project administrators to make changes to workflows and screens used by their projects. |
| Browse Project | This is the permission for users to browse and view the project and its issues. If a user does not have the Browse Project permission for a given project, the project will be hidden from them, and notifications will not be sent. |
| Manage Sprints | This is the permission to control who can perform sprint-related operations, such as creating and starting a sprint, on an agile board. This is only applicable to Jira Software. |
| View Development Tools | This is the permission for users to have access to information from Jira's development tools integration, such as code commits and build results. |
| View Read-Only Workflow | This is the permission for users to view a read-only diagram of the workflow. When the user has this permission, there will be a View Workflow link next to the issue's status. |
The issue permissions and their descriptions are as follows:
| Issue permissions | Description |
| Assignable User | This is the user that can be assigned to issues. |
| Assign Issues | This is the permission for users to assign issues to different users. |
| Close Issues | This is the permission for users to close issues. |
| Create Issues | This is the permission for users to create issues. |
| Delete Issues | This is the permission for users to delete issues. |
| Edit Issues | This is the permission for users to edit issues. |
| Link Issues | This is the permission for users to link issues together (if issue linking is enabled). |
| Modify Reporter | This is the permission for users to change the value of the Reporter field. |
| Move Issues | This is the permission for users to move issues. |
| Resolve Issues | This is the permission for users to resolve issues and set values for the Fix For Version field. |
| Schedule Issues | This is the permission for users to set and update due dates for issues. |
| Set Issue Security | This is the permission for users to set issue security levels to enable issue-level security. Refer to upcoming sections to learn more about issue security. |
| Transition Issues | This is the permission to transition issues through the workflow. |
The voters and watchers permissions and their descriptions are as follows:
| Voters and Watchers permissions | Description |
| Manage Watchers | This is the permission to manage the watchers list of issues (add/remove watchers). |
| View Voters and Watchers | This is the permission to view the voters and watchers list of issues. |
The comment permissions and their descriptions are as follows:
| Comments permissions | Description |
| Add Comments | This is the permission for users to add comments to issues. |
| Delete All Comments | This is the permission to delete all comments. |
| Delete Own Comments | This is the permission to delete your own comments. |
| Edit All Comments | This is the permission for users to edit comments made by all users. |
| Edit Own Comments | This is the permission to edit your own comments. |
The attachment permissions and their descriptions are as follows:
| Attachments permissions | Description |
| Create Attachments | This is the permission to add attachments to issues (if an attachment is enabled). |
| Delete All Attachments | This is the permission to delete all attachments to issues. |
| Delete Own Attachments | This is the permission to delete attachments to issues added by you. |
The time tracking permissions and their descriptions are as follows:
| Time tracking permissions | Description |
| Delete Own Worklogs | This is the permission to delete worklogs made by you. |
| Delete All Worklogs | This is the permission to delete all worklogs. |
| Edit Own Worklogs | This is the permission to edit worklogs made by you. |
| Edit All Worklogs | This is the permission to edit all worklogs. |
| Work On Issues | This is the permission to log work done on issues (if time tracking is enabled). |
As you can see, even though the list cannot be modified, Jira provides you with a very comprehensive list of permissions that will cover almost all your permission needs.
With this many permissions, it would be highly inefficient if you had to create them individually for each project you have. With permission schemes, Jira lets you define your permissions once and apply them to multiple projects.