Permissions overview 1

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community


Board permissions can be divided into two parts — board administration permissions and board usage permissions.

Board administration permissions cover functionality for changing the configuration of a board. For example, changing columns, customizing cards, etc. Board administration can be assigned to groups or users. Learn more in Configuring a board.

Board usage permissions cover functionality for the usage of a board. For example, creating sprints, ranking issues, etc. Board usage permissions are derived from project permissions. This is described in more detail below.

Jira Software functions by permission

In the Jira Software documentation, most configuration options are described as being restricted to either Jira administrators, project administrators, or board administrators.  

  • A Jira administrator is a user with the Jira administrators global permission.  
  • A project administrator is a user with the Administer projects project permission for a particular project. By default, the Administer projects permission is assigned to the administrators group through the Administrators role for projects. Additionally, to perform sprint-related actions, users need the Manage sprints permission for all projects in the origin board. The origin board is the board where the sprint was originally created.
  • A board administrator is a user that has been added to Administrators for a particular board. By default, the administrator of a board is the user who created it.

Board administration

Function / Functional area

Jira
admin 

Project
admin 
Board adminNotes
Create board(tick)

(tick)

(tick) 

If you create a board via Boards (in the top navigation bar > Manage Board, you won't be able to share it unless you have the Create shared objects global permission.

If you create the board in one of the following ways, you don't need the Create Shared Objects global permission to share the board:

  • Creating a project (where a board is created for the project by default)
  • Setting up Jira Software for the first time (where you're prompted to create a project, which also creates a board for the project)
  • Copying a board (the copied board will be shared with the same users as the original board)
Simplify workflow(tick)N/A(tick)The board must meet other criteria as well. Check Simplified workflow for more detail.
Add status(tick)(warning)(tick)

The project must be currently using an Agile Simplified Workflow.

You must be a Jira admin or board admin to view the board configuration. In addition, you must be a project admin for the one project that is on the board.

Remove status(tick)(warning)(tick)

The project must be currently using an Agile Simplified Workflow.

You must be a Jira admin or board admin to view the board configuration. In addition, you must be a project admin for the one project that is on the board.

All other board configuration functions(tick)N/A(tick)N/A

Board usage

Board usage permissions are derived from project permissions. Depending on the complexity of your board's filter query, you may need further consideration when configuring the Manage sprints permission for users. For more information on the impact of complex filters and the ways to simplify your filter query, refer to Using Manage Sprints permission for advanced cases.

FunctionPermission Level

Backlog — Sprints

Move sprint footer
  • Manage sprints permission (for all projects on the board)
  • Schedule issues permission
  • Edit Issues permission
Move issue (reorder/rank)

Schedule issues permission and Edit issues permission

Note: The permissions aren't required if you only move issues across the sprint footer without changing the order of the issues.

Start sprint

Manage sprints permission (for all projects on the board)

Note: The permission is similar to Create version. Board ownership doesn't matter.

Create sprint

Manage sprints permission (for all projects on the board)

Note: This permission applies even if a sprint that is about to start doesn't include issues from all projects queried by the board.

Edit sprint information

Manage Sprints permission (for all projects on the board)

Note: This can only be done in the backlog.

Reorder sprintManage Sprints permission (for all projects on the board)
Delete sprint

Manage Sprints permission (for all projects on the board)

Add issue to sprintSchedule Issues permission and Edit Issues permission
Active sprints — Sprints
Add issue to sprintSchedule Issues permission and Edit Issues permission
Complete sprint

Manage sprints permission (for all projects on the board)

Note: This can only be done in active sprints.

Remove issue from sprintSchedule issues permission and Edit issues permission
Backlog — Epics
Create epicCreate issues permission
Rename epicEdit issues permission
Rank epicSchedule issues permission
Add issue to epicEdit issues permission
Remove issue from epicEdit issues permission
Backlog — Versions
Create versionProject admin permission or Jira admin permission
Edit versionProject admin permission or Jira admin permission
Add issue to versionEdit issues permission
Remove issue from versionEdit issues permission
Last modified on Aug 18, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.