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

Project permissions are created within Permission Schemes, which are then assigned to specific projects.

Project permissions can be granted to:

  • 個々のユーザー
  • グループ
  • プロジェクトロール
  • Issue roles such as 'Reporter', 'Project Lead' and 'Current Assignee'
  • 'Anyone' (例: 匿名アクセスを許可する)
  • A (multi-)user picker custom field.
  • A (multi-)group picker custom field. This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.

The following table lists the different types of project permissions and the functions they secure. Note that project permissions can also be used in workflow conditions.

On this page:

プロジェクト権限

説明

プロジェクト管理

Permission to administer a project in JIRA. This includes the ability to edit project role membership, project components, project versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description').

プロジェクトの参照

Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted via Issue Security). Many other permissions are dependent on this permission, e.g. the 'Work On Issues' permission is only effective for users who also have the 'Browse Projects' permission.

View Version Control

Permission to view the version control information (e.g. CVS, Subversion, FishEye, etc) for an issue. Note that for CVS, to view the Version Control information the project needs to be associated with at least one Repository.

「読み取り専用」ワークフローの表示

Permission to view the project's 'read-only' workflow when viewing an issue. This permission provides the 'View Workflow' link against the 'Status' field of the 'View Issue' page.

課題の権限

説明

課題の割り当て

Permission to assign issues to users. (See also Assignable User permission below)

割り当て可能なユーザー

課題への割り当てが可能な権限 (注: 課題を割り当てをする権限は含みません。上記の課題の割り当てを参照ください。)

課題のクローズ

Permission to close issues. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission.

課題の作成

Permission to create issues in the project. (Note that the Create Attachments permission is required in order to create attachments.) Includes the ability to create sub-tasks (if sub-tasks are enabled).

課題の削除

課題を削除する権限。この権限を割り当てるグループやプロジェクト ロールは慎重に検討してください。通常は管理者のみに与えられます。課題を削除すると、そのユーザーがコメントの削除権限や添付ファイルの削除権限を持たない場合であっても、課題のコメントや添付ファイルがすべて削除される点にご注意ください。ただし、課題の削除権限には、個々のコメントや添付ファイルを削除する権限は含まれません。

課題の編集

Permission to edit issues (excluding the 'Due Date' field — see the Schedule Issues permission). Includes the ability to convert issues to sub-tasks and vice versa (if sub-tasks are enabled). Note that the Delete Issue permission is required in order to delete issues. The Edit Issue permission is usually given to any groups or project roles who have the Create Issue permission (perhaps the only exception to this is if you give everyone the ability to create issues — it may not be appropriate to give everyone the ability to edit too). Note that all edits are recorded in the Issue Change History for audit purposes.

課題のリンク

Permission to link issues together. (Only relevant if Issue Linking is enabled).

報告者の修正

課題の [報告者] を変更する権限。これによって、ユーザーは、誰かの代理で課題を作成できるようになります。この権限は一般に、管理者にのみ付与する必要があります。

課題の移動

１つのプロジェクトから別のプロジェクト、または同じプロジェクト内の１つのワークフローから別のワークフローへ課題を移動する権限。ユーザーは課題の作成権限を持っているプロジェクトにのみ課題を移動できます。

課題の解決

Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission.

課題のスケジュール

Permission to schedule an issue — that is, set and edit the 'Due Date' of an issue.

課題のセキュリティの設定

Permission to set the security level on an issue to control who can access the issue. Only relevant if issue security has been enabled.

投票とウォッチャーの権限

説明

ウォッチャー一覧の管理

Permission to manage (i.e. view/add/remove users to/from) the watcher list of an issue.

投票とウォッチャーの表示

Permission to view the voter list and watcher list of an issue. Also see the Manage Watcher List permission.

コメントの権限

説明

コメントの追加

Permission to add comments to issues. Note that this does not include the ability to edit or delete comments.

すべてのコメントの削除

Permission to delete any comments, regardless of who added them.

自身のコメントの削除

Permission to delete comments that were added by the user.

すべてのコメントの編集

Permission to edit any comments, regardless of who added them.

自身のコメントの編集

Permission to edit comments that were added by the user.

添付ファイルの権限

説明

添付ファイルの作成

Permission to attach files to an issue. (Only relevant if attachments are enabled). Note that this does not include the ability to delete attachments.

すべての添付ファイルの削除

Permission to delete any attachments, regardless of who added them.

自分の添付ファイルの削除

Permission to delete attachments that were added by the user.

時間管理の権限

説明

課題の作業ログ

Permission to log work against an issue, i.e. create a worklog entry. (Only relevant if Time Tracking is enabled).

すべての作業ログの削除

Permission to delete any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission.

自分の作業ログの削除

Permission to delete worklog entries that were added by the user. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission.

すべての作業ログの編集

Permission to edit any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission.

自分の作業ログの編集

Permission to edit worklog entries that were added by the user. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission.

権限スキーム

What is a Permission Scheme?

権限スキームは、上記のプロジェクト権限に割り当てられたユーザー、グループ、ロールをセットにしたものです。どのプロジェクトも権限スキームを持っています。一つの権限スキームを複数のプロジェクトに関連づけることができます。

Why Permission Schemes?

In many organisations, multiple projects have the same needs regarding access rights. (For example, only the specified project team may be authorised to assign and work on issues).

権限スキームは、プロジェクトごとに個別にアクセス権を設定する手間を省きます。いったん権限スキームを設定すると、同じ種類のアクセス要件を持つプロジェクトすべてに、そのスキームを適用できます。

Creating a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select 'Administration' > 'Issues' > 'Permission Schemes' to open the 'Permission Schemes' page, which lists all the Permission Schemes currently available in your JIRA installation.
    (tick) Keyboard shortcut: 'g' + 'g' + start typing 'permission schemes'
  3. Click the 'Add Permission Scheme' link.
    Screenshot 1: The 'Permission Schemes' page
  4. In the 'Add Permission Scheme' form, enter a name for the scheme, and a short description of the scheme. Click the 'Add' button.
    Screenshot 2: The 'Add Permission Scheme' form
  5. You will return to the 'Permission Schemes' page which now contains the newly added scheme.
    Screenshot 3: the 'View Permission Schemes' page, showing the newly added scheme

Adding Users, Groups or Roles to a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select 'Administration' > 'Issues' > 'Permission Schemes' to open the 'Permission Schemes' page.
    (tick) Keyboard shortcut: 'g' + 'g' + start typing 'permission schemes'
  3. Locate the permission scheme of interest and click its name (or click the 'Permissions' link in the 'Operations' column) to show a list of permissions.
  4. Click the 'Add' link in the 'Operations' column, which displays the 'Add Permission' page.
    Screenshot 4: Project Permissions
  5. After selecting one or more permissions to add and who to add the selected permissions to, click the 'Add' button. The users/groups/roles will now be added to the selected permissions. Note that project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimise the number of permission schemes in your system.
    Screenshot 5: Add Users To Permissions
  6. 必要なユーザー、グループ、ロールがすべて権限に追加されるまで、直前の 2 ステップを繰り返します。

Deleting Users, Groups or Roles from a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select 'Administration' > 'Issues' > 'Permission Schemes' to open the 'Permission Schemes' page.
    (tick) Keyboard shortcut: 'g' + 'g' + start typing 'permission schemes'
  3. This will display the 'Managing Project Permissions' page (see above).
  4. Location the permission scheme of interest and click its name (or click the 'Permissions' link in the 'Operations' column) to show the list of 'Project Permissions' (above).
  5. Click the '(Delete)' link in the "Users / Groups / Roles" column next to the name of the user, group or project role you wish to delete.

Associating a Permission Scheme with a Project

  1. Log in to 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 at the top of the screen.
  3. Click 'Projects' and select the project of interest. You will now see the 'Project Summary' screen (see Defining a Project).
  4. On the lower right, in the 'Permissions' section, click the name of the current scheme (e.g. 'Default Permission Scheme') to display the details of the project's current permission scheme.
  5. If using JIRA 4.4.1 or later, click the 'Actions' dropdown menu and choose 'Use a different scheme'.
    (info) If using JIRA 4.4.0, click the pencil icon instead.
    Screenshot 6: The Project Permissions page (JIRA 4.4.1 and later)
  6. On the 'Associate Permission Scheme to Project' page, which lists all available permission schemes, select the permission scheme you want to associate with the project.
    Screenshot 7: The 'Associate Permission Scheme to Project' page
  7. 「関連付け」ボタンをクリックし、プロジェクトを権限ボタンに関連づけます。

Deleting a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select 'Administration' > 'Issues' > 'Permission Schemes' to open the 'Permission Schemes' page, which lists all the Permission Schemes currently available in your JIRA installation.
    (tick) Keyboard shortcut: 'g' + 'g' + start typing 'permission schemes'
  3. Click the 'Delete' link (in the 'Operations' column) for the scheme that you want to delete.
  4. A confirmation screen will appear. To delete click 'Delete' otherwise click 'Cancel'.
  5. スキームが削除され、関連するすべてのプロジェクトは既定の権限スキームに自動的に関連付けられます。（既定の権限スキームは削除できないので、注意してください。）

(info) See also Minimising the number of Permission Schemes and Notification Schemes.

Copying a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select 'Administration' > 'Issues' > 'Permission Schemes' to open the 'Permission Schemes' page, which lists all the Permission Schemes currently available in your JIRA installation.
    (tick) Keyboard shortcut: 'g' + 'g' + start typing 'permission schemes'
  3. Click the 'Copy' link (in the 'Operations' column) for the scheme that you want to copy.
  4. コピー元のスキームと同じ権限を持ち、同じユーザー、グループ、ロールがその権限に割り当てられた新しいスキームが作成されます。



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.