プロジェクト権限の管理
Project permissions are managed in two ways:
Jira admins manage project permissions for company-managed projects through permission schemes. This page discusses permission schemes for company-managed projects in detail.
Project admins manage project permissions for team-managed projects through custom roles. Read more about custom roles in team-managed projects.
Every company-managed project has a permission scheme. A permission scheme grants users, groups, or roles their permissions in your company-managed projects. Read the details of each available project permission.
You can't edit project permissions or roles on the Free plan for Jira, and you can't configure work-level security on any Free plan (including Jira Service Management). Find out more about how permissions work in Free plans. To take advantage of Jira's powerful project permission management features, upgrade your plan.
Like other schemes in Jira, changes you make a to permission scheme update the permissions for any of the company-managed projects associated with the scheme. This makes it easy for Jira admins to manage the permissions of many projects at once, without having to adjust each project’s settings individually. Once a permission scheme is set up, it can be applied to all projects that have the same type of access requirements.
Permission schemes set permissions at the project level. You may still want to adjust permissions across your Jira site through global permissions. For example, allowing users to create shared objects like filters, or make bulk work item changes. Read more about global permissions.
権限スキームの作成
権限スキームを作成するには、次の手順を実行します。
Select Settings (), then select Work items.
From the sidebar, select Permission Schemes. The Permission Schemes page opens. It displays a list of all the permission schemes in your Jira site and the projects that use each scheme.
[権限スキームを追加] を選択します。[権限スキームを追加] フォームが表示されます。
新しいスキームに名前を付け、スキームの簡単な説明を追加します。説明は、将来スキームを識別するのに役立ちます。
[追加] を選択します。
新しく追加したスキームが [権限スキーム] ページに表示されますが、これはまだ使用されていません。スキームを適切に使用するには、次の手順を実行する必要があります。
Add users, groups, and roles to the scheme and grant their project permissions.
Associate the scheme with the projects that should use it.
ユーザー、グループ、ロールを権限スキームに追加し、プロジェクト権限を付与する
The permission scheme itself is just an object that Jira references when checking permission in your projects. To make the scheme useful, you need to grant users, groups, and/or roles their project permissions in the scheme.
To add users, groups, or roles to a permission scheme, and grant them project permissions:
Select Settings (), then select Work items.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
更新する権限スキームを見つけ、[操作] 列で [権限] を選択して、スキームを表示します。
For each permissions available, select Update to grant the permission to a user, group, or role. This displays the Grant permission dialog. Read the details of each available project permission.
[権限の付与] ダイアログで、権限を付与するユーザーを選択して [付与] ボタンをクリックします。権限は次のユーザーに付与できます。
Individual users, which your site admin can invite to your Jira products. Find out about inviting users.
Groups, which your site admin sets up. Find out about groups.
Project roles, which Jira administrators can set up in advance. Find out about project roles.
Work item roles such as Reporter, Project lead, and Current Assignee.
Public, which can make work items public to the internet. Find out about anonymous access.
(マルチ) ユーザー ピッカー カスタム フィールド
(マルチ) グループ ピッカー カスタム フィールド。これはグループ ピッカー カスタム フィールドか、グループ名が値として含まれている (マルチ) 選択リストです。
Some permissions are dependent upon others to ensure that users can perform the actions needed. For example, for a user to be able to Edit work items in the project, they first must be able to access the project with the Browse project permission. Or, for a user to be able to resolve a work item, they must also be able to transition the work item. Read the details of each available project permission.
すべてのユーザーに権限を付与する
Granting the Browse project permission to Public means work items from projects that use the permission scheme are publicly viewable on the internet. You may legitimately want to grant public access to some projects and work items on your site, like in the case of a public bug tracker. Find out about anonymous access.
Some permissions require product access
Some project permissions are only usable if your users also have access to the Atlassian product that checks the permission. For example, if you give someone the permission to Edit work items in a software project, they still require product access to Jira to gain that permission.
If you add people to a role that grants these permissions, make sure they have product access to Jira (for software projects) or Jira Service Management (for service projects). If not, they may encounter problems and won’t get the full benefit of the features you intended them to use. Otherwise, these users will see a read-only version of the projects you intend them to work on.
Only your site admin can grant individuals product access. Find out about product access.
The Browse project permission may make project details visible to all users in directories and while searching Jira
There’s a known issue when granting a User custom field value, Reporter, Current assignee, or Group custom field value the Browse project permission. In these cases, a project becomes visible to any logged in user on your Jira site.
The issue is caused by an intentional design in Jira’s backed that couples the Browse project and View work item permissions.
Project titles will be visible to some admins
Organization admins and authorized Guard Detect admins can see project titles in audit logs and security alerts. They won’t be able to see project content, just the title.
Use project roles to help scale your Jira site as your company grows
We recommend assigning permissions through project roles, rather than individual users or group access. Referencing project roles rather than users or groups in your permissions can help you minimize the number of permission schemes in your system. They can help you save time when managing users across your site, and how they can act in each project you create in Jira. Read more about project roles in Jira.
権限スキームと企業管理対象プロジェクトの関連付け
Once you have your project permission grants figured out, you can put the scheme into effect by associating it with the projects its meant to govern.
To associate a permission scheme with a company-managed project:
Choose Settings (), then select Projects.
Search for and select the project you want to change permissions for.
Next to the name of your project in the sidebar, select More actions (•••), then Project settings.
サイドバーから [権限] を選択します。現在の権限スキームが表示されます。
[アクション] ドロップダウン メニューをクリックして、[別のスキームの使用] を選択します。
On the Associate Permission Scheme to Project page, select the permission scheme you want to associate with the project.
Click the Associate button to associate the project with the permission scheme.
Your project's permissions are updated and the project now follows your permission scheme. Any updates you make the scheme or its grants apply immediately to the project associated with the scheme.
権限スキームからのユーザー、グループ、ロールの削除
権限スキームからユーザー、グループ、ロールを削除するには、次の手順を実行します。
Select Settings (), then select Work items.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Locate the permission scheme of interest and click its name to show the list of project permissions (above).
ユーザー、グループ、ロールを削除する権限の 削除 リンクをクリックします。
削除するユーザー、グループ、またはロールを選択し、[削除] ボタンを押します。
権限スキームのユーザーやグループを削除しても、これらのユーザーが Jira から完全に削除されるわけではありません。サイト管理者のみが Jira サイトからユーザーを削除できます。アトラシアン サイトからユーザーを完全に削除する方法の詳細をお読みください。
権限スキームのコピー
Some projects may require only minor tweaks to an existing permission scheme. In these cases, you can use the existing permission scheme as a starting point for a new scheme. Copying a permission scheme gives you this quick start to tweak a scheme and meet the requirements for a new project.
権限スキームをコピーするには、次の手順を実行します。
Select Settings (), then select Work items.
From the sidebar, select Permission Schemes. The Permission Schemes page opens. It displays a list of all the permission schemes in your Jira site and the projects that use each scheme.
[アクション] 列で、コピーしたいスキームの [コピー] リンクをクリックします。
コピー元のスキームと同じ権限を扱い、それらを同じユーザー、グループ、またはロールを割り当てる新しいスキームが作成されます。このスキームは「<権限スキーム名> のコピー」という名前で、権限スキームのリストに表示されます。
権限スキームの削除
Every company-managed project requires a permission scheme to function. If you delete a permission scheme that’s associated with one or more projects, those projects will fall back to using the Default Permission Scheme. You can't delete the default permission scheme.
権限スキームを削除するには、次の手順を実行します。
Select Settings (), then select Work items.
From the sidebar, select Permission Schemes. The Permission Schemes page opens. It displays a list of all the permission schemes in your Jira site and the projects that use each scheme.
[アクション] 列で、削除したいスキームの列の [削除] リンクをクリックします。
In Jira, you can delete the Default software scheme, but this is superficial. Jira will recreate this permission scheme if you create a new company-managed software project, and associate it to your new project.
この内容はお役に立ちましたか?