Failures in Automation for Jira rules involving third-party actions

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

With Automation for Jira 9.1.1 update, automation rules that incorporate third-party actions, such as ScriptRunner scripts, are experiencing failures. These failures are noted without further details in the Automation Audit Log as shown below:

Failures in Automation for Jira rules involving third-party actions sample audit log failure

Diagnosis

  • The problem began after upgrading Automation for Jira to 9.1.1

  • Upon configuring DEBUG logging level the following two debug packages com.codebarrel.automation and com.codebarrel.jira.plugin.automation, within the atlassian Jira log files, we encountered a message stating: "has been skipped because it didn't pass the validation."

    ATLASSIAN-JIRA.LOG

    1 2024-05-31 08:30:00,671+0000 http-nio-8080-exec-25 url: /jira/rest/cb-automation/latest/project/10000/rule/1/execute/SCRUM-23; user: admin DEBUG xxx 510x1768x1 xxxx  /rest/cb-automation/latest/project/10000/rule/1/execute/SCRUM-23 [c.c.j.p.a.service.execution.JiraAutomationExecutionService] Sync execution of Rule(id=1, name='Sample Scriptrunner rule') for AutomationEvent with traceId='d105dd50-1017-4ca5-900c-8576261cba33' has been skipped because it didn't pass the validation.

  • Rule actor lacks the global Jira Administrator permission

Cause

Scriptrunner's "run a script" action always necessitates Jira admin permission. However, in earlier versions, this requirement was not adequately validated and was only implemented after the Jira 9.1.1 update.

Solution

Grant global Jira Administrator permission to the rule actor.

Updated on July 15, 2024

Still need help?

The Atlassian Community is here for you.