Automation rules using 3rd party add-on components fail if the rule actor is not granted global admin permission

XMLWordPrintable

    • Severity 2 - Major
    • Warranty

      Issue

      Automation Rules which are using a 3rd party add-on component such as the ScriptRunner "Run a script" action fail to execute if the Rule Actor is not granted Global Jira Admin permission:

      Versions

      This bug impacts any Automation For Jira (A4J) version from 9.1.1.

      Steps to replicate

      1. Install ScriptRunner (or any other 3rd party add-on that comes with its own automation components)
      2. Configure an automation rule using the "Run a script" action from ScriptRunner
      3. Set the rule actor to a Jira user who is not granted Global Jira Admin permission
      4. Execute the rule

      Expected results

      The rule should execute without an error, regardless if the rule actor has Global Jira Admin permission or not.

      Actual results

      The rule fails with the "FAILURE" status, and without any error shown in the Audit Logs.

      Workaround

      Please refer to the KB article Failures in Automation for Jira rules involving third-party actions

        1. RuleUsingScriptFailure.png
          205 kB
          Julien Rey

            Assignee:
            Haribaskar Govindasamy
            Reporter:
            Julien Rey (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: