Sometimes it’s important to understand how far your Jira application has strayed from the default configuration. Was that setting there from the beginning or did an application administrator add it eons ago?
Default permission schemes (Jira Software Cloud)
To find out, visit Admin > Issues > Permission schemes in your application. Then use this baseline list to compare your Jira settings to the default.
Initial settings for Jira Cloud and Jira Server/Data Center v8.15 are included below. I keep fresh and untouched application instances around so you don’t have to!
Scheme name: Default Permission Scheme
Ability to administer a project in Jira.
Granted to:
Ability to browse projects and the issues within them.
Granted to:
Ability to manage sprints.
Granted to:
Allows users in a software project to view development-related information on the issue, such as commits, reviews and build information.
Granted to:
Users with this permission may view a read-only version of a workflow.
Granted to:
Users with this permission may be assigned to issues.
Granted to:
Ability to assign issues to other people.
Granted to:
Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.
Granted to:
Ability to create issues.
Granted to:
Ability to delete issues.
Granted to:
Ability to edit issues.
Granted to:
Ability to link issues together and create linked issues. Only useful if issue linking is turned on.
Granted to:
Ability to modify the reporter when creating or editing an issue.
Granted to:
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project they have the create permission for.
Granted to:
Ability to resolve and reopen issues. This includes the ability to set a fix version.
Granted to:
Ability to view or edit an issue’s due date.
Granted to:
Ability to set the level of security on an issue so that only people in that security level can see the issue.
Granted to:
Ability to transition issues.
Granted to:
Ability to manage the watchers of an issue.
Granted to:
Ability to view the voters and watchers of an issue.
Granted to:
Ability to comment on issues.
Granted to:
Ability to delete all comments made on issues.
Granted to:
Ability to delete own comments made on issues.
Granted to:
Ability to edit all comments made on issues.
Granted to:
Ability to edit own comments made on issues.
Granted to:
Users with this permission may create attachments.
Granted to:
Users with this permission may delete all attachments.
Granted to:
Users with this permission may delete own attachments.
Granted to:
Ability to delete all worklogs made on issues.
Granted to:
Ability to delete own worklogs made on issues.
Granted to:
Ability to edit all worklogs made on issues.
Granted to:
Ability to edit own worklogs made on issues.
Granted to:
Ability to log work done against an issue. Only useful if Time Tracking is turned on.
Granted to:
Scheme name: Default software scheme
Same as the Jira Cloud “Default Permission Scheme” except:
Ability to manage sprints.
Granted to:
Scheme name: Default software scheme
Ability to administer a project in Jira.
Granted to:
Also includes a checkbox to grant extended project administration permissions.
Extended project administration
Ability to browse projects and the issues within them.
Granted to:
Ability to edit sprint name and goal.
Granted to: none
Ability to manage sprints.
Granted to:
Ability to start and complete sprints.
Granted to: none
Allows users in a software project to view development-related information on the issue, such as commits, reviews and build information.
Granted to:
Users with this permission may view a read-only version of a workflow.
Granted to:
Users with this permission may be assigned to issues.
Granted to:
Ability to assign issues to other people.
Granted to:
Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.
Granted to:
Ability to create issues.
Granted to:
Ability to delete issues.
Granted to:
Ability to edit issues.
Granted to:
Ability to link issues together and create linked issues. Only useful if issue linking is turned on.
Granted to:
Ability to modify the reporter when creating or editing an issue.
Granted to:
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project they have the create permission for.
Granted to:
Ability to resolve and reopen issues. This includes the ability to set a fix version.
Granted to:
Ability to view or edit an issue’s due date.
Granted to:
Ability to set the level of security on an issue so that only people in that security level can see the issue.
Granted to: none
Ability to transition issues.
Granted to:
Ability to manage the watchers of an issue.
Granted to:
Ability to view the voters and watchers of an issue.
Granted to:
Ability to comment on issues.
Granted to:
Ability to delete all comments made on issues.
Granted to:
Ability to delete own comments made on issues.
Granted to:
Ability to edit all comments made on issues.
Granted to:
Ability to edit own comments made on issues.
Granted to:
Users with this permission may create attachments.
Granted to:
Users with this permission may delete all attachments.
Granted to:
Users with this permission may delete own attachments.
Granted to:
Ability to delete all worklogs made on issues.
Granted to:
Ability to delete own worklogs made on issues.
Granted to:
Ability to edit all worklogs made on issues.
Granted to:
Ability to edit own worklogs made on issues.
Granted to:
Ability to log work done against an issue. Only useful if Time Tracking is turned on.
Granted to:
Scheme name: Default software scheme
Same as the Jira Server “Default Permission Scheme”.
These types of Jira have archival features and additional permissions. Same as the Jira Server “Default Permission Scheme” plus:
Ability to browse archived issues from a specific project.
Granted to: none
Ability to archive issues for a specific project.
Granted to: none
Ability to restore issues for a specific project.
Granted to: none
Rachel Wright
Author, Jira Strategy Admin Workbook
Industry Templates, LLC
Traveling the USA in an RV
46 accepted answers
1 comment