Low Issue Summary
In case the A4J rule contains ScriptRunner's "Execute a ScriptRunner Script" action and Actor user doesn't have sufficient permissions for executing it (require Jira administrators global permission), rule execution will fail.
However, such a rule could be successfully saved/published, and at that moment, no validation against the required permission will happen.
Steps to Reproduce
- Create any A4J rule. The rule could have any trigger/action configuration and the only requirement it should include "Execute a ScriptRunner Script" action. It doesn't matter whether the action will run an external script or an inline one.
- Set as rule's Actor a user account without Jira administrators global permission.
- Publish/save rule.
Expected Results
The publishing rule should fail, and an error reported that the Actor user doesn't have sufficient permission to successfully execute the rule.
Actual Results
The rule could be saved/published successfully without any error. However, further rule execution will fail due to a lack of required permissions.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
- is related to
-
JIRAAUTOSERVER-1104 Automation rules using 3rd party add-on components fail if the rule actor is not granted global admin permission
-
- Closed
-
- links to
- mentioned in
-
Page Failed to load
Closing this bug as invalid since the scriptRunner actions do not require "Jira administrator" permission anymore. Please see related bug for more details