JIRA Software: Levels of Administration in JIRA
How are global permissions and project permissions managed in JIRA Software?
There are two levels of permissions within the JIRA platform.
This table lists the different global permissions and the functions they secure:
JIRA System Administrators
Permission to perform all JIRA administration functions.
Permission to perform most JIRA administration functions.
Note that a user with the JIRA Administrators permission will be able to log in at any time, but may have restricted functions depending on their application access.
Permission to view a list of all JIRA user names and group names. Used for selecting users/groups in popup screens. Enables auto-completion of usernames in most 'User Picker' menus and popups.
Note that the Assign User permissions also allows a limited version of this on a per-project basis.
Create Shared Objects
Manage Group Filter Subscriptions
Permission to manage (create and delete) group filter subscriptions.
Permission to execute the bulk operations within JIRA:
Project permissions are created within permission schemes, which are then assigned to specific projects by JIRA Administrators. We can also grant permissions for project level. Project permissions are able to be granted based on:
- Individual users
- Project roles
- Issue roles such as 'Reporter', 'Project Lead', and 'Current Assignee'
- 'Anyone' (e.g. to allow anonymous access)
- A (multi-)user picker custom field.
- A (multi-)group picker custom field. This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.
Note that some permissions are dependent upon others to ensure that users can perform the actions needed. For example, in order for a user to be able to resolve an issue, that user must be granted both the Transition Issue permission and the Resolve Issue permission.