Jira Service Management 権限エラーを解決する

カスタムの権限スキームを使用する際、権限設定が標準の権限スキームの設定と異なると、以下のような権限エラーが発生します。

権限スキームエラーの説明

Jira Service Management は、ユーザーの権限スキームと Jira Service Management の標準の権限スキームとの差異をエラーと見なします。エラーには、次の 2 つのカテゴリがあります。

Critical errors (red): These errors either cause certain administration functionality to be disabled (for example you cannot add agents to your service project), or impact the day-to-day use of your service project (for example customers cannot log in to the Customer Portal). This table describes what Jira Service Management considers as critical errors. You cannot dismiss these error messages, as you must fix them in order for Jira Service Management to return to normal operation.
Non-critical errors (yellow): Permission scheme differences that do not impact how Jira Service Management works are considered as non-critical errors. You can dismiss these error messages if you do not want to use the standard permission setup.

エラーを解決する

You can resolve the permission errors by changing the permission scheme yourself or using the Fix permissions button in the error message.

What does the Fix permissions button do?

The Fix permissions button on the message disassociates your custom permission scheme with the service project, creates a copy of your permission scheme with the name of <your_permission_scheme [number]>, and associates this new scheme with the project. The new scheme fixes the errors by:

Granting the standard permissions to the Administrators and Service Desk Team roles, and the Service Project Customer - Portal Access security type.
Removing the Service Desk Customers role from all the permissions assigned.
他の権限セットアップは変更なし

元の権限スキーム	新しい権限スキーム
元の名前は"プロジェクト OA 用 JIRA サービスデスク権限スキーム" 次の権限が標準権限スキームとは異なる内容でセットアップされています。 User John Smith has the Browse Projects permission. This is a minor error. The Service Desk Customers role has the Create Issues permission. This is a major error. The Service Project Customer - Portal Access security type does not have the Create Issues permission. This is the major error.	After you click Fix permissions, the 'Jira Service Management Permission scheme for Project OA' permission scheme is dissociated with the project, and a new permission scheme called 'Jira Service Management Permission scheme for Project OA 1' will be applied to your service project. User John Smith will still have the Browse Projects permission. The Service Desk Customers role is removed from the Create Issues permission. The Service Project Customer - Portal Access security type will be granted the Create Issues permission.

元の権限スキーム

新しい権限スキーム

元の名前は"プロジェクト OA 用 JIRA サービスデスク権限スキーム"

次の権限が標準権限スキームとは異なる内容でセットアップされています。

User John Smith has the Browse Projects permission. This is a minor error.
The Service Desk Customers role has the Create Issues permission. This is a major error.
The Service Project Customer - Portal Access security type does not have the Create Issues permission. This is the major error.

After you click Fix permissions, the 'Jira Service Management Permission scheme for Project OA' permission scheme is dissociated with the project, and a new permission scheme called 'Jira Service Management Permission scheme for Project OA 1' will be applied to your service project.

User John Smith will still have the Browse Projects permission.
The Service Desk Customers role is removed from the Create Issues permission.
The Service Project Customer - Portal Access security type will be granted the Create Issues permission.

重大な権限エラーとは

重大な権限エラーにより、Jira Service Management の特定の機能が無効になります。

エラー	説明
The Administrators role does not have the following required permissions: プロジェクトの参照プロジェクト管理課題の編集	No Browse Projects permission = Administrators cannot access the service desk. No Administer Projects permission = Administrators cannot modify settings of the service desk. No Edit Issues permission = Administrators cannot edit issues.
The Service Project Customer - Portal Access security type does not have the following required permissions: プロジェクトの参照課題の作成コメントの追加	No Browse Projects permission = Customers cannot access the Customer Portal of the service desk, that is they cannot log in. No Create Issues permission = Customers cannot create requests on the Customer Portal. No Add Comments permission = Customers cannot add comments to their requests.
The Service Desk Customers role is granted any permission directly.	Granting permissions to this role gives customers access to Jira functions. Customers should only have access to a Customer Portal and permissions should be granted to the Service Project Customer - Portal Access security type. 結果として、管理者はカスタマーをサービスプロジェクトに追加できなくなります。オープンなサービスプロジェクトは制限されます。パブリックサインアップが無効になります。
The Service Desk Team role does not have the following required permissions: プロジェクトの参照課題の編集	No Browse Projects permission = Agents cannot see the service project. No Edit Issues permission = Agents cannot edit issues.
The Service Desk Team role is granted the Administer Projects permission.	エージェントにプロジェクト管理権限を付与することは、すべてのエージェントがサービスプロジェクトの管理者になることを意味します。これは重大なセキュリティ問題です。Jira Service Management のエージェント管理機能が無効になります。その結果、管理者はエージェントを追加できなくなります。

この内容はお役に立ちましたか?

正確ではなかった明確ではなかった関係なかった

さらにヘルプが必要ですか?

アトラシアンコミュニティをご利用ください。

コミュニティに質問