企業管理対象プロジェクトの権限

Project permissions are managed in two ways:

1. Jira administrators manage project permissions for company-managed projects through permission schemes. This page discusses the individual permission grants available to company-managed permission schemes.

2. Project admins manage permissions for team-managed projects through custom roles. Read more about custom roles in team-managed projects.

Here’s a list of the permissions you can grant to define permissions in your company-managed software, service project, or business projects through permissions schemes. Read more about permission schemes.

Administration permissions

Manage work item layouts

This permission allows people to edit work item layouts in their company-managed project. This is an ability that all Jira Admins have by default, but can also be delegated to any user or role, allowing teams to directly manage and add fields (including existing global custom fields) to the layout of the work items in the project.

To grant this permission, the screen underlying the layout of work items must not be shared with other projects. To see if the screen associated with the work item layout is shared:

1. Go to the work item layout tab in the project settings of the relevant company-managed project

2. Click on the screen listed underneath the work item layout you are evaluating

3. At the top-left of the screen, the count of projects using this screen will be displayed. If the count is greater than 1, that means this screen is shared

ワークフローを編集

This permission allows users to make modifications (e.g changing statuses and transitions) to exisiting isolated workflows in their company-managed project. This is an ability that all Jira Admins have by default, but can also be delegated to any user or role, allowing teams to directly manage and customise their project's workflows.

To grant this permission, the workflow must not be shared with other projects. To see if the workflow is shared:

• グローバル設定から（Jira 管理者のみ）：

  1. Go to Settings (), then Work items

  2. Select the Workflows tab

  3. Look at the workflow you are evaluating. If there is more than one project or workflow scheme listed next to the workflow, it is a shared workflow.

• From project settings:

  1. Go to the settings of the company-managed project where the workflow is used

  2. Select the Workflows tab

  3. Look at the workflow you are evaluating. If the count of projects listed underneath the workflow is greater than one, it is a shared workflow.

プロジェクト権限

The following permissions define access to functionality within your company-managed projects and the work items those projects contain. They don’t define access or permissions to your Jira site, generally. Only site admins can grant people access to your Jira site. Find out how to give people access to your Atlassian products.

Administer projects

This permission allows people access to your project's settings.

このユーザーは以下が可能です。 

• edit project role membership 

• edit project components, 

• edit project versions,

• edit some project details like project name, URL, project lead, and project description

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

Typically, system administrators need this permission to help you configure projects. For that reason, they don't need product access and won't take a seat in your site’s plan.

バージョンの管理

This permission allows people to create, release, archive, merge, edit and delete versions. If you’re a project admin that already has the Administer projects permission, you’ll still be able to manage versions, regardless of whether you’ve been granted the Manage versions permission.

Versions (also referred to as releases) represent specific points in time for a project, like a planned release of new features or bug fixes. They are used to organize and track work items towards a particular milestone. More about how to view and manage project versions.

Browse projects

This permission allows people to view the project in the Projects directory, and view individual work items in the project and while searching Jira (except work items that have been restricted via work-level security).

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

集計データを表示する 

この権限によって、ボード、バックログ、デプロイ ビューのインサイトが有効化されます。時間の経過とともに、この権限を持つユーザーは JQL の結果、クエリ、またはレポートによって表示される他の集計データ ソースを閲覧できる場合があります。

• A project's average estimations or work item count. This means a user can see how much effort has been planned all up, even if they can’t see the estimated effort for every work item.

• 作業タイプの名前。ユーザーが特定の作業タイプにアクセスできなくても、スプリントの上位 5 つの作業タイプのいずれかである場合、その名前がインサイトに表示されます。

• The name of your epics. Although some work items may be hidden by your work-level security, the epics they’re linked to can be shown on the board or through the cycle time report.

• チームサイクル期間またはデプロイ頻度。通常は作業レベルのセキュリティによって非表示になっている作業項目が公開されて、ユーザーはこれらのメトリックを手動で計算できます。

[集計データを表示] 権限を無効にすると、ユーザーはこの権限によって裏付けられた集計データを表示できなくなります。

これには、ボード、バックログ、デプロイ ビューに関するインサイトと一部のレポートが含まれます。将来的には、JQL および検索結果が含まれる可能性もあります。

スプリントの管理

This permission allows people to create, start, and complete sprints in your project. This includes adjusting the sprint duration and goal.

This permission depends on product access to Jira. Find out about giving people access to your Atlassian products.

Sprints are a concept from agile methodology, specifically a way of working called Scrum. Typically, sprints are managed by team leaders or designated Scrum masters. Find out about sprints, Scrum, and how to practice agile methods in Jira.

Depending on the complexity of your board's filter query, you may need further consideration when configuring the Manage sprints permission for users. For example, if a board contains sprints from multiple projects (including service projects), users need the Manage sprints permission in every project to successfully complete sprints. For more information on the impact of complex filters, and ways to simplify your filter query, see Using Manage Sprints permission for advanced cases.

There are some sprint actions (for example, adding work items to sprints, removing work items from sprints) that require the Schedule work items and Edit work items permissions to be successful.

Find out about planning sprints in Jira.

開発ツールの参照

Permission to view the development panel, which provides you with just enough information to evaluate the status of a work item's build data in a connected development tool, at a glance. Find out about the development panel.

This permission depends on product access to Jira. Find out about giving people access to your Atlassian products.

(読み取り専用) ワークフローの表示

この権限は、作業項目を表示するときに [ワークフローを表示] リンクを提供します。 

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

作業項目に関する権限

To perform actions on work item permissions, users need permission to view the project the work item permissions belongs to. This is granted by the Browse projects permission in your permission scheme. Once the user has the Browse projects permissions, the various work item permissions listed below may be granted.

Archive work items

This permission can be granted to any role and allows people to archive any work item in your project, which includes its associated field values and comments. This helps people clean up their projects and maintain site performance and provides an alternative to the Delete work items permission.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

More about giving people access to your Atlassian products

作業項目を割り当てる

This permission allows people to change the value of the Assignee field on any of your project’s work items. It doesn’t allow people to be assigned work items (see the Assignable user permission).

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

 Find out about giving people access to your Atlassian products.

この権限を持つチーム メンバーは、作業のさまざまなステージでタスクを引き渡すことができます。

割り当て可能なユーザー

This permission allows people to be assigned work items, meaning their username can be used to complete the Assignee field on any of your project’s work items. It doesn’t allow people to be assign work items to other users in your site (see the Assign work items permission).

This permission may depend on product access to be useful:

• In software projectsprojects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

This permission gives people the ability to update work items. When someone is assigned a work item, we notify them to view the work item. This permission is essential for core team members on any project.

Close work items

This permission allows people to set the Resolution field to a closed state on a work item based on a the conditions of your work item's workflow.

This permission requires the Transition work items and Resolve work items to be useful.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

 Find out about giving people access to your Atlassian products.

Jira の場合

• A work item is open if its resolution field isn't set.

• A work item is closed if its resolution field has a value, for example “Fixed” or “Can't reproduce”.

There are two ways to close a work item using a condition in your workflow:

1. Set the resolution field automatically via a post function. Find out about advanced workflow configuration.

2. Prompt the user to choose a resolution via a screen. Find out about transition screens.

This permission is used mainly for software or service teams who use quality assurance engineers to test whether fixes work as intended. You can set your permissions to allow developers to transition a work item to a done status but keep it open. Then, only allow your tester to close the work item when they’ve verified the fix.

Create work items

This permission allows people to create work items in your project, including subtasks if you’ve enabled subtasks on your site. Find out about subtasks.

注意:

• When a user is granted the Create work items permission for a project, they’ll see the project on the Create work item screen, even if they don’t have the Browser projects permission for the same project.

• Users won’t be able to add attachments to work items unless they’re also granted the Create attachments permission.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

This permission can be granted to anyone logged in to the Jira site, regardless of product access - this gives you the benefit of allowing anyone to create work items in a project. For example, you might do this to allow customers to report bugs or create feature suggestions for a product you’re developing.

However, some teams might choose to limit this permission to only their core team members, for security reasons or to maintain the cleanliness of their work items.

Delete work items

この権限を使用すると、ユーザーがコメントの削除権限や添付ファイルの削除権限を持っていない場合でも、関連するフィールド データ、コメント、作業時間ログエントリを含めた、プロジェクト内のあらゆる作業項目の情報を削除できます。ただし、作業項目の削除権限には、個々のコメントまたは添付ファイルを削除する権限は含まれません。

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

この権限は一般に、チーム リーダーまたはプロジェクト管理ロールにのみ付与することが望まれます。一般に、作業項目を削除することは推奨されません。作業項目のステータスを完了カテゴリステータスに変更するほうが、不要な作業項目をクリーンアップするよりも推奨されます。作業項目のステータスを変更すると、チームタスクに対してタスクが実行されたアクションが報告者、担当者、ウォッチャーに通知されます。

Edit work items

This permission allows people to alter the summary and description, and change the value of fields that aren’t overridden by another permission (like the Assign work items, Modify reporters, or Schedule work items permissions). This permissions also allows people to convert work items to subtasks or vice versa. Find out about work items and subtasks.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian product.

オープンな組織ではチームに対し、作業でタスクを表示する際にフィールドを調整することで互いの作業を最新の状態に保つことを奨励します。スタンドアップ ミーティング、計画ミーティング、ボード整理セッション、またはプロジェクトのキックオフ ミーティングなどの共通のミーティング時にタスクのレビューを実施する可能性があるチーム メンバーにとって、説明を明確化し、フィールドを更新できることは非常に便利です。厳格なコンプライアンスまたはトレーサビリティ要件を持つ組織は、この権限をチーム リーダーまたはプロジェクト マネージャー用に予約する場合があります。

Link work items

This permission allows people to link work items in your project to one another, or to work items in other projects on your site. To view the link properly, they need the same permission in the target project or service desk. This permission is only relevant if you’ve enabled work item linking. Find out about work item linking.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

報告者の変更

This permission allows people to change the value of the default Reporter field on any of your project’s work items. The Reporter field is automatically set to the work items creator at the time the work item is made. This allows someone to create work items on behalf of someone else.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

Move work items

This permission allows people to move a work item to another project or service project on your Jira site, or to change the work item to a different work type (making the work item follow a different workflow).

This permission requires the Create work items permission in the target project or service desk to be useful.

Resolve work items

この権限を持つユーザーは、[解決状況] フィールド値の設定またはクリアが可能です。また、作業項目の [修正バージョン] フィールドを確認することもできます。作業項目をクローズする機能は含まれません (作業項目のクローズ権限を参照)。

This permission requires the Transition work items permission to be useful.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

Restore archived work items

This permission can be granted to any role and allows people to restore any work item in your project, which includes its associated field values and comments. A restored work item will appear in the project, dashboard, backlog and boards, and can be edited if needed.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

More about giving people access to your Atlassian product.

Schedule work items

This permission allows people to set or modify the value of the Due date field on your project’s work items. On a company-managed Scrum or Kanban board, this permission also allows people to reorder work items (“rank”) on the board and backlog.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

作業項目セキュリティの設定

This permission allows people to set the security level of specific work items in the project, changing who can view and interact with a specific work item. This is typically reserved for project managers, administrators, or other team leaders. Find out about work item security.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

作業項目をトランジションする

This permission allows people to view a work item’s underlying workflow in the project and update the status of any of your project's work items. They can move any work item through the workflow, triggering any workflow post functions that may be associated with the transition along the way. Find out about workflows.

It doesn’t allow people to set the Resolution field or close work items in your project (see the Resolve work items and Close work items permissions).

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

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

The following permissions are only useful to people who are able to view the project. To make these permissions meaningful, first grant users, groups or roles the Browse projects permission in your permission scheme.

ウォッチリストの管理

This permission allows people to add or remove people from a work item’s watch list.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

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

This permission allows people to see who’s watching any work item in your project.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

コメント権限

The following permissions are only useful to people who are able to view the project. To make these permissions meaningful, first grant users, groups or roles the Browse projects permission in your permission scheme.

コメントの追加

This permission allows people to comment on any work item in your software and business projects, or add internal notes to requests in your service projects.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

これにはコメントの編集または削除を行う権限は含まれていない点にご注意ください。

すべてのコメントの削除

This permission allows people to remove any comment added by anyone on any of your software or business projects' work items, or delete any internal notes (and customer comments!) added to any request in a service project. It’s a bit of a super power.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

For traceability and historical investigations, we recommend preserving all work item comments. They can help you trace how a project went, or how an interaction could be improved in the future. For that reason, you may reserve this permission for team leaders, human resource managers, or other management roles.

自分のコメントの削除

This permission allows people to remove any comments they’ve added to any work item in your project, or any internal comment they’ve added to requests in a service project.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

Typically, anyone who can comment on a work item (by having the Add comments permission) should be able to remove their own comments. This practice can help clarify work if people leave erroneous or inaccurate comments. Organizations with strict compliance or traceability requirements may consider restricting this permission to preserve an accurate historical record throughout a work item’s lifecycle.

すべてのコメントの編集

This permission allows people to alter the content of any comment or internal note added by anyone on any of your project’s work items.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

オープンな組織では、チームで互いのコメントを編集して、スペル ミスやリンク切れなどの軽微な問題を修正したり、コミュニケーションの流れを整理したりすることが推奨されます。厳格なコンプライアンスまたはトレーサビリティ要件を持つ組織は、この権限をチーム リーダーまたはプロジェクト マネージャー用に予約する場合があります。

自分のコメントの編集

This permission allows people to alter the content of any comments they’ve added to work items in software or business projects, or any internal comment they’ve added to requests in a service project.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

通常、[コメントの追加] 権限を使用して作業項目にコメントできるユーザーは、自分のコメントを変更したり、スペルミスやリンク切れなどのマイナー問題を修正できることが望ましいです。コンプライアンスまたはトレーサビリティについて厳格な要件が課される組織では、この権限を制限して、作業項目のライフサイクルを通じて正確な履歴レコードを保持することを検討することが望まれます。

添付ファイルの権限

The following permissions are only useful to people who are able to view the project. To make these permissions meaningful, first grant users, groups or roles the Browse projects permission in your permission scheme.

添付ファイルの作成

This permission allows people to attach files to any work item in your project. This permission is relevant if attachments are enabled. Find out about attachments.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

Typically, any team member or collaborator may need this permission to help describe their work. Find out about attaching files and screenshots to work items.

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

This permission allows people to remove any attachments added by anyone on any of your project’s work items.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

While some teams may reserve this permission for management roles, open organizations can benefit from granting this power to autonomous team members. For example, if the work item requires images from a designer to help describe the work, it might be beneficial for team members to keep attachments up to date, even if they aren’t the owner of the original attachment.

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

This permission allows people to remove any file or image they attached to any work item in your project.

This permission doesn’t depend on specific product access to be useful. You may grant this permission to anyone logged in to your Jira site.

Typically, anyone who can attach files to a work item (by having the Add attachments permission) should be able to remove their own attachments. This practice can help clarify work where many versions of a file or image are uploaded throughout the course of working on the work item. Organizations with strict compliance or traceability requirements may consider restricting this permission to preserve an accurate historical record throughout a work item’s lifecycle.

時間管理権限

The following permissions are only useful to people who are able to view the project. To make these permissions meaningful, first grant users, groups or roles the Browse projects permission in your permission scheme.

The following permissions are only useful if you’ve enabled time tracking on your Jira site. Find out about time tracking.

This permission may depend on product access to be useful:

• In software projects, people must have product access to Jira to use this permission.

• In service projects, people must have product access to Jira Service Management to use this permission.

• In business projects, you may grant this permission to anyone logged in to your Jira site.

Find out about giving people access to your Atlassian products.

作業項目に取り組む

This permission allows people to interact with the time tracking field on any of your project’s work items.

この権限を持つユーザーは、タスクに費やした時間と完了までの残りの時間を示す作業ログ エントリ (プロセス中に行った作業の簡単な説明を含む) を作成することができます。

すべての作業ログの削除

This permission allows people to remove any work log entry added by anyone on any of your project’s work items.

通常、他のユーザーの作業ログ エントリの削除は、チーム リーダーまたはその他の管理ロール専用の権限です。

自分の作業ログの削除

This permission allows people to remove the time they logged, the time they estimated as remaining, and the description of any work log entry they added to any of your project’s work items.

Typically, people who actively work and log time in your project need to delete their own work logs in case of data entry errors.

すべての作業ログの編集

This permission allows people to alter the time logged, time remaining, and description of any work log entry added by anyone on any of your project’s work items.

通常、他のユーザーの作業ログ エントリの調整は、チーム リーダーまたはその他の管理ロール用に予約されます。

自分の作業ログの編集

This permission allows people to alter the time they logged, the time they estimated as remaining, and the description of any work log entry they added to any of your project’s work items.

Typically, people who actively work and log time in your project will need to adjust their own work logs in case of data entry errors or changes to the work’s scope or requirements.