要約

The error below is observed in the audit logs of an automation rule when the Comment on issue action is executed:

<Jira_User_Name>, you do not have the permission to comment on this issue.

The purpose of this article is to explain how to diagnose this error and fix it.

環境

Jira Data Center on any version from 9.0.0.

根本原因

Root Cause 1 - Lack of permissions due to the Project Permission Scheme

A possible cause is the fact that the Actor for the affected automation rule does not have permission to comment on the affected issue due to the Permission Scheme associated to the project.

Root Cause 2 - Lack of permissions due to properties added to specific statuses in the workflow configuration

Another possible cause is the fact that the Actor for the affected automation rule does not have permission to comment on the affected issue due to some properties used in the Workflow configuration which are preventing all of some users from commenting on issues that are in a specific status.

診断

根本原因の診断 1

Follow the steps below to check if this root cause is relevant:

1. 影響を受ける課題にアクセスします。
2. 課題コンテキストの [管理者] ドロップダウン メニューをクリックします。
3. [権限ヘルパー] を選択します。
4. フォームに次のとおり入力します。
   • ユーザー: <ルールのアクター>
   • Permission: "Add Comments"
5. Click on submit
6. If the test fails as illustrated below, then this root cause is relevant
   

根本原因の診断 2

Follow the steps below to check if this root cause is relevant:

• Take note of the workflow status of the Jira issue that the rule failed to edit
• Edit the workflow associated to this issue and switch to the diagram view
• Click on the status and check it's properties
• If you see property keys related to issue editing, such as jira.permission.comment.user or jira.permission.comment.denied as illustrated in the 2 screenshots below, then this root cause is relevant:
  • 例 1:
    
  • 例 2:
    

ソリューション

Ensure that the Rule Actor is granted the permission to add comments to the issue. Depending on the root cause identified in the Diagnosis section, the solution will consist in:

• Either adjusting the Permission Scheme configuration
• Or the Workflow Properties