Manage project roles

Project roles are a flexible way to associate users and/or groups with particular projects. Project roles also allow for delegated administration:

• Jira administrators define project roles — that is, all projects have the same project roles available to them.

• Project administrators assign members to project roles specifically for their project(s).
  A project administrator is someone who has the project-specific 'Administer Project' permission, but not necessarily the global 'Jira Administrator' permission.

Project roles can be used in:

• permission schemes

• email notification schemes

• issue security levels

• comment visibility

• workflow conditions

Project roles can also be given access to:

• issue filters

• dashboards

Project roles are somewhat similar to groups, the main difference being that group membership is global whereas project role membership is project-specific. Additionally, group membership can only be altered by Jira administrators, whereas project role membership can be altered by project administrators. Every project has a project lead and every project component has a component lead. These individual roles can be used in schemes, issues and workflows, just like project roles. You assign project/component leads when defining projects or managing components respectively.

Using project roles

Project roles enable you to associate users with particular functions. For example, if your organization requires all software development issues to be tested by a Quality Assurance person before being closed, you could do the following:

1. Create a project role called Quality Assurance.

2. Create a permission scheme called Software Development, in which you assign the 'Close Issue' permission to the Quality Assurance project role.

3. Associate the Software Development permission scheme with all software development projects.

4. For each software development project, add the appropriate Quality Assurance people to the Quality Assurance project role.

Default project roles

When you install Jira applications, the Administrators role is automatically created, along with project roles specific to each application. You can create, edit, and delete project roles according to your organization's requirements.

Viewing project roles

1. Choose > System.

2. Under SECURITY, select Project roles. The Project Role Browser displays, which contains a list of all the project roles in your Jira site.

3. To see where a project role is used, click the View Usage link. This displays a list of the project role's associated permission schemes, email notification schemes, issue security levels, and workflow conditions.

4. Click any of the View links in the Project Role Members Per Project column to see which users/groups are associated with a project role for a particular project.

Adding a project role

To define a new project role:

1. Choose > System.

2. Under SECURITY, select Project roles. The Project Role Browser displays, which contains a list of all the project roles in your Jira site.

3. Under Add Project Role at the bottom of the page, enter your desired role's name and a description

4. Click the Add Project Role button.

To add members to the role:

1. Click on Manage Default Members in the Actions column for your newly created project role.

2. Click Edit under Default Users or Default Groups.

3. Enter group names in the Add user(s) to project role field. Or, select the user picker icon  to add individual users.

4. Click the Add button.

Once a new project role is created, it is available to all projects. Project administrators can then assign members to the project role for their project (see Managing project role membership).

Deleting a project role

To delete a project role, locate the project role in the project role browser (see 'Viewing Project Roles' above), and click the Delete link. The confirmation screen that follows lists any permission schemes, email notification schemes, issue security levels, and workflow conditions that use the project role.

Deleting a project role removes any assigned users and groups from that project role, for all projects. Be aware of the impact this may have. For example, if the project role membership was the sole conveyor of a permission for a user, then the user will no longer have that permission.

Editing a project role

To edit the name and description of a project role, locate the project role in the project role browser (see Viewing project roles above), and click the Edit link. 

Assigning members to a project role

A project role's members are assigned on a project-specific basis. To assign users/groups to a project role for a particular project, please see Managing project role membership.

To see/edit all the project roles to which a particular user belongs, for all projects, click the Project Roles link in the user browser.

Specifying 'default members' for a project role

The default members for a project role are users and groups that are initially assigned to the project role for all newly created projects. The actual membership for any particular project can then be modified by the project administrator.

The default members consist of the Default Users plus the Default Groups shown in the project role browser (see 'Viewing Project Roles' above).

To add to the Default Users or the Default Groups for a project role, click the corresponding 'Edit' link.

For example, if a user called Susie needs to have administration permissions for all newly created projects, you could add her to the Default Users for the 'Administrator' project role as follows:

1. Open the project role browser (see 'Viewing Project Roles' above).

2. Click the Manage Default Members link.

3. Click the Edit link in the Administrators column (next to 'None selected').

4. In the 'Assign Default Users to Project Role' screen, click the User Picker icon.

5. Locate Susie in the 'User Picker' popup window, then click the Select button.

6. In the 'Assign Default Users to Project Role' screen, click the Add button.