Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

A JIRA project role is a flexible way to associate users and/or groups with a particular project.

Unlike groups, which have the same membership throughout JIRA, project roles have specific members for each project. Users may play different roles in different projects.

This page contains instructions for managing membership of existing project roles. For information on creating and using project roles, please see Managing project roles.

On this page:

Viewing project role members

To see which users and groups belong to each project role for a particular project:

  1. Log into JIRA as a project administrator. (A project administrator is someone who has the project-specific permission 'Administer Project', but not necessarily the global permission 'JIRA Administrators'.)
  2. Click the 'Administration' link on the top bar.
  3. This will display the Administration page, showing a list of projects which you have permission to manage. Click the project of interest.
  4. This will display the Project Administration page. Click the 'View members' link:
  5. This will display the Manage Project Role Membership page, showing the project role members for this project:
    !project_roles-manage_roles_project.png|title="View project roles"!From this page you can assign users/groups to and remove them from project roles, as described below.

    *A project administrator is someone who has the project-specific 'Administer Project' permission, but not necessarily the global 'JIRA Administrator' permission.

Assigning a user to a project role

  1. Open the 'Manage Project Role Membership' page as described in 'Viewing project role members' (above).
  2. Click the 'Edit' link in the 'Users' column for the project role you wish to edit.
  3. This will display the 'Assign Users to Project Role' page:

    The users currently in the project role are listed on the left-hand side of the page. Type the username(s) in the 'Add User' box on the right-hand side of the page, then click the 'Add' button.

Removing a user from a project role

  1. Open the 'Manage Project Role Membership' page as described in 'Viewing project role members' (above).
  2. Click the 'Edit' link in the 'Users' column for the project role you wish to edit.
  3. This will display the 'Assign Users to Project Role' page. The users currently in the project role are listed on the left-hand side of the page. Tick the user(s) you wish to remove from the project role, then click the 'Remove' button.

Assigning a group to a project role

  1. Open the 'Manage Project Role Membership' page as described in 'Viewing project role members' (above).
  2. Click the 'Edit' link in the 'Groups' column for the project role you wish to edit.
  3. This will display the 'Assign Groups to Project Role' page:

    The groups currently in the project role are listed on the left-hand side of the page. Type the group name(s) in the 'Add Group' box on the right-hand side of the page, then click the 'Add' button.

Group membership can only be viewed/edited by people with the global 'JIRA Administrator' permission. Project administrators may therefore prefer to assign users, rather than groups, to their project roles.

Removing a group from a project role

  1. Open the 'Manage Project Role Membership' page as described in 'Viewing project role members' (above).
  2. Click the 'Edit' link in the 'Groups' column for the project role you wish to edit.
  3. This will display the 'Assign Groups to Project Role' page. The groups currently in the project role are listed on the left-hand side of the page. Tick the group(s) you wish to remove from the project role, then click the 'Remove' button.

A project role need not have any user or group assigned to it, although project administrators should be careful with this. Depending on how a project role is utilised (e.g. if the project's permission scheme is using project roles), it is possible that not having anyone in a particular project role could make some project activities unavailable.

  • No labels