Documentation for JIRA 5.1.x. Documentation for other versions of JIRA is available too.

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.

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

プロジェクト ロール メンバーの表示

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

  1. Log in to JIRA as a project administrator. (A project administrator is someone who has the Administer Project project-specific permission, but not necessarily the JIRA Administrators global permission.)
  2. Click the Administration link at the top of the page.
  3. Click Projects and select the project of interest from the dropdown menu. The 'Project Summary' page (see Defining a Project) for your selected project is shown.
    (tick) Keyboard shortcut: g + g + start typing project
  4. Locate the People section at the right of the 'Project Summary' page (see Screenshot 1 below) and click the View Project Roles link to display the People page (see Screenshot 2 below).
    Screenshot 1: The 'People' section of the 'Project Summary' page

  5. The People page is displayed, from where you can manage the project role membership as described below.
    Screenshot 2: The 'People' page

On this page:

ユーザーをプロジェクト ロールに割り当てる

  1. Open the People page (see Screenshot 2) as described in 'Viewing project role members' above.
  2. Hover over the Users column for the project role in which you are interested (e.g. Administrators) and click the yellow box which appears. The users and groups will become editable (see Screenshot 3).
  3. Type the name of the user(s) you wish to add to this project role.
    (info) The Browse Users global permission is required to search for users in the Users column. If you do not have this permission, you will need to specify the exact name of the user(s), followed by the 'Enter' key after each user specified.
  4. 更新ボタンをクリックします。


Screenshot 3: Editing project role membership

Removing a user from a project role

  1. Open the People page (see Screenshot 2) as described in 'Viewing project role members' above.
  2. Hover over the Users column for the project role in which you are interested (e.g. Administrators) and click the yellow box which appears. The users and groups will become editable (see Screenshot 3).
  3. Click the x next to the name of the user(s) you wish to remove from this project role.
  4. 更新ボタンをクリックします。

Assigning a group to a project role

  1. Open the People screen (see Screenshot 2) as described in 'Viewing project role members' above.
  2. Hover over the Groups column for the project role in which you are interested (e.g. Administrators) and click the yellow box which appears. The users and groups will become editable (see Screenshot 3).
  3. Type the name of the group(s) you wish to add to this project role.
    (info) The Browse Users global permission is required to search for groups in the Groups column. If you do not have this permission, you will need to specify the exact name of the group(s), followed by the 'Enter' key after each group specified.
  4. 更新ボタンをクリックします。

Since group membership can only be edited by users with the JIRA Administrator global 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 People page (see Screenshot 2) as described in 'Viewing project role members' above.
  2. Hover over the Groups column for the project role in which you are interested (e.g. Administrators) and click the yellow box which appears. The users and groups will become editable (see Screenshot 3).
  3. Click the x next to the name of the group(s) you wish to remove from this project role.
  4. 更新ボタンをクリックします。

A project role need not have any users or groups assigned to it, although project administrators should be careful with this. Depending on how a project role is used (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.



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.