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

On this page:

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.

プロジェクト権限

説明

プロジェクト管理

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). Users without this permission will not know that the project exists.

View Version Control

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

課題の作成

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 set and edit the 'Due Date' of issues.

課題の移動

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

課題の割り当て

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

割り当て可能なユーザー

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

課題の解決

Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues.

課題のクローズ

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

報告者の修正

Permission to modify the 'Reporter' of an issue. This allows a user to create issues 'on behalf of' someone else.

課題の削除

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

課題のリンク

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

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

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 view the voter list and watcher list of an issue.

ウォッチャー一覧の管理

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

コメントの追加

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

すべてのコメントの編集

コメントを編集する権限。 誰が追加したコメントでも編集できます。

自身のコメントの編集

自分が追加したコメントを編集する権限。

すべてのコメントの削除

コメントを削除する権限。 誰が追加したコメントでも削除できます。

自身のコメントの削除

自分が追加したコメントを削除する権限。

添付ファイルの作成

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 log work done against an issue, i.e. create a worklog entry. (Only relevant if Time Tracking is enabled).

自分の作業ログの編集

Permission to edit worklog entries that were added by the user. (Only relevant if Time Tracking is enabled).

すべての作業ログの編集

Permission to edit any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled).

自分の作業ログの削除

Permission to delete worklog entries that were added by the user. (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).

権限スキーム

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. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Schemes', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all of the Permission Schemes that JIRA currently has. Click the 'Add Permission Scheme' link.
  5. In the 'Add Permission Scheme' form, enter a name for the scheme, and a short description of the scheme. Click the 'Add' button.
  6. 「権限スキーム」ページに戻ると、ページには新しく追加したスキームが含まれています。

Adding Users, Groups or Roles to a Permission Scheme

  1. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  2. Click the 'Permissions' link or on the name of the Permission Scheme to show a list of permissions
  3. Click the 'Add' link in the 'Operations' column.
  4. This will display the 'Add Permission' page. 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.
  5. 必要なユーザー、グループ、ロールがすべて権限に追加されるまで、直前の 2 ステップを繰り返します。
  6. To delete a user/group/role from a permission click the 'Delete' link in the "Users / Groups / Roles" column.

Associating a Permission Scheme with a Project

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. A list of projects is displayed
  4. Select the project you want by clicking on the project name. This will display the project details
  5. Click the 'select scheme' link beside the Permission Scheme caption.
  6. This will bring up a list of Permission Schemes. Select the Permission Scheme that you want to associate with this project.
  7. 関連付け」ボタンをクリックし、プロジェクトを権限ボタンに関連づけます。

Deleting a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all the Permission Schemes that are currently defined in your JIRA system. Click the 'Delete' link for the scheme that you want to delete.
  5. A confirmation screen will appear. To delete click 'Delete' otherwise click 'Cancel'.
  6. スキームが削除され、関連するすべてのプロジェクトは既定の権限スキームに自動的に関連付けられます。(既定の権限スキームは削除できないので、注意してください。)

Copying a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all of the Permission Schemes that JIRA currently has. Click the 'Copy' link for the scheme that you want to copy.
  5. コピー元のスキームと同じ権限を持ち、同じユーザー、グループ、ロールがその権限に割り当てられた新しいスキームが作成されます。

その他のリソース

  • Permission scheme overview tutorial video - Watch this short tutorial video to see how to set up a new permission scheme to control which users can perform which operations on an issue. Please note the JIRA version of the tutorial video before watching.