Jira roles and project permissions

Jira projects use a layered permission model to control what users can do within a project.

Access is determined by three layers working together:

Together, these layers determine what each user can do within a Jira project.

Permission capabilities

Permission capabilities define the types of actions that can be performed in a Jira project.

Permission capability	Description
Browse project	Allows users to view the project and its issues
Create issues	Allows users to create new issues
Edit issues	Allows users to modify issue details
Assign issues	Allows users to assign issues to users
Transition issues	Allows users to move issues through workflow statuses
Add comments	Allows users to comment on issues
Manage sprints	Allows users to create and manage sprints
Project administration	Allows users to manage project settings and permissions

These capabilities represent the actions that may be allowed in a project.
However, they do not determine who can perform these actions.

Project roles organise users based on their responsibilities within a project.

Instead of assigning permissions directly to individual users, Jira assigns permissions to roles, and users are placed into those roles.

Role	Description
Administrator	Manages project configuration, including assigning users to roles and managing project settings
Developer	Works on issues, including editing, transitioning, and resolving tasks
User	Creates issues, comments on issues, and tracks project progress

Users may be assigned to multiple project roles.

The permissions assigned to project roles depend on the permission scheme applied to the project.

The following table shows an example of how permissions may be assigned to common Jira project roles.

Note: The exact permissions available to each role may differ depending on the permission scheme configured for your project.

Permission	Administrator	Users	Developer
Administer Projects	✓
Browse projects	✓	✓	✓
Manage Sprint	✓
Start/Complete Sprint	✓
View Development Tools	✓		✓
View Read-only Workflow	✓	✓	✓

Permission	Administrator	Users	Developer
Archive Issues	✓
Assignable User	✓		✓
Assign Issues	✓		✓
Close Issues	✓		✓
Create Issues	✓	✓	✓
Delete Issues	✓		✓
Edit Issues	✓		✓
Link Issues	✓	✓	✓
Modify Reporter	✓
Move Issues	✓		✓
Resolve Issues	✓		✓
Schedule Issues	✓		✓
Set Issue Security	✓	✓	✓
Transition Issues	✓	✓	✓

Permission	Administrator	Users	Developer
Manage Watchers	✓		✓
View Voters and Watchers	✓		✓

Permission	Administrator	Users	Developer
Add Comments	✓	✓	✓
Delete All Comments	✓
Delete Own Comments	✓	✓	✓
Edit All Comments	✓		✓
Edit Own Comments	✓	✓	✓

Permission	Administrator	Users	Developer
Create Attachments	✓	✓	✓
Delete All Attachments	✓
Delete Own Attachments	✓	✓	✓

Permission	Administrator	Users	Developer
Delete All Worklogs	✓
Delete Own Worklogs	✓	✓	✓
Edit All Worklogs	✓		✓
Edit Own Worklogs	✓	✓	✓
Work On Issues	✓		✓

When a Jira project is created through Console, certain SHIP-HATS roles are mapped to Jira project roles.

SHIP-HATS role	Jira role	Description
Project Admin (PA)	Administrator	Assigned automatically when the Jira project is created and responsible for managing project configuration
Users	Developer or User	Assigned based on the user’s responsibilities within the project

Important

Being a SHIP-HATS Project Admin does not automatically grant access to a Jira project.
Users must have a valid Jira licence provisioned via TechBiz.
Users must also be assigned appropriate project permissions.

Jira permissions are additive.

A user may receive permissions through:

All permissions combine to determine the user’s effective access.

Additional restrictions, such as issue security settings, may further limit visibility even when project permissions are granted.

Permissions available to project roles are defined in the permission scheme applied to the project.

A permission scheme maps project permissions to roles, users, or groups.