標準の権限
This page shows the permission configuration for a standard JIRA Service Desk permission scheme.
- To see an overview of how permissions are set up for a service desk, see JIRA Service Desk permissions.
- If you want to customize the permission scheme, make sure that the mandatory permissions are assigned to the roles. See Using custom permission schemes.
- If you run into permission-related problems, see Resolving permission scheme errors.
プロジェクト権限 | ユーザー/グループ/プロジェクトロール | 説明 |
|---|---|---|
プロジェクト管理 | プロジェクト ロール (Administrators) | Permission to administer a project. 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. | |
開発ツールの参照 | Permission to view the Development panel, which displays information from Bitbucket, GitHub, Stash, FishEye, Crucible and Bamboo, if JIRA is integrated with compatible versions of these applications. For older versions of Stash and FishEye or for Subversion and CVS, this grants permission to view the related source code commits for an issue, in the 'Commits' and 'Source' tabs. Note that for CVS, to view the related source code commits, 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 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 transition (change) the status of an issue. | |
| 課題のスケジュール | Permission to schedule an issue — that is, to edit the 'Due Date' of an issue. In older versions of JIRA this also controlled the permission to view the 'Due Date' of an issue. | |
| 課題の移動 | Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission. | |
課題の割り当て | ユーザに課題を割り当てる権限。課題の割り当てドロップダウンでのユーザーのオートコンプリートも可能です。(以下の割り当て可能ユーザー権限も参照) | |
割り当て可能なユーザー | 課題を割り当てられる権限。(これには課題を割り当てる権限は含まれていない点にご注意ください。課題の割り当て権限を参照)。 | |
| 課題の解決 | 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 close issues. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission. | |
報告者の修正 | 課題の [報告者] を変更する権限。これによって、ユーザーは、誰かの代理で課題を作成できるようになります。この権限は一般に、管理者にのみ付与する必要があります。 | |
課題の削除 | 課題を削除する権限。この権限を割り当てるグループやプロジェクト ロールは慎重に検討してください。通常は管理者のみに与えられます。課題を削除すると、そのユーザーがコメントの削除権限や添付ファイルの削除権限を持たない場合であっても、課題のコメントや添付ファイルがすべて削除される点にご注意ください。ただし、課題の削除権限には、個々のコメントや添付ファイルを削除する権限は含まれません。 | |
課題のリンク | 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. Also see the Manage Watcher List permission. | |
ウォッチャー一覧の管理 | 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 edit any comments, regardless of who added them. | |
自身のコメントの編集 | Permission to edit comments that were added by the user. | |
| すべてのコメントの削除 | Permission to delete any comments, regardless of who added them. | |
| 自身のコメントの削除 | Permission to delete 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 log work 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). 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 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 delete any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission. |