Resolve 'Actor Permission' Automation Error in Jira Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
Resolve 'Actor Permission' errors in automation logs, including issues with viewing permissions or deleted items.
Diagnosis
You can find the following errors in the audit log:
"Actor does not have permission to view one or more issues, or the issue was deleted"
"Actor does not have permission to view the event that triggered this execution"
Cause
Parallel executions, due to which the deleted issue got picked by the automation.
This is a known limitation, and we have the following request to improve this behavior.
AUTO-32 - Rule orchestration - allows the switch between parallel and sequential execution of Automation Rules
The rule actor does not have the required permission to execute the rule actions.
The atlassian-addons-project-access role does not have the required permissions.
Solution
Solution to Cause 1
When an issue is created, the Issue Creation Trigger immediately performs the defined actions. The actor must have the necessary permissions to view, modify, transition, or delete the issue.
When multiple automation rules run during the Issue Creation event, a rule may fail the permission check if the issue is deleted first.
Automation for Jira uses a rule processing queue to efficiently handle rule executions in your instance. Rule executions are queued to ensure optimal performance, but the number of simultaneous processes is not controlled.
Multiple automation rules triggered by the Issue Creation event may not execute immediately and are queued for processing. If the "Delete issue" action occurs first, subsequent rules may fail to associate the Issue ID, resulting in an error message: "Actor does not have permission to view the event that triggered this execution."
Combining rules with the same trigger would also help in this scenario.
Solution to Cause 2
Check the rule actor and permission scheme to ensure the actor has the correct permission to perform actions.
Check if the issue security scheme is blocking the rule actor from performing actions, and correct the permissions.
Solution to Cause 3
The Automation for Jira actor will only work if the atlassian-addons-project-access role has the desired permissions.
Helpful resources:
Was this helpful?