Upgrading Automation for Jira to version 9.2.1 may cause a failure when updating automation rules

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 9.2.2
    • Affects Version/s: 9.2.1
    • Component/s: Configuration
    • Severity 2 - Major

      Issue Summary

      Automation for Jira (A4J) version 9.2.1 was released on 2024-11-04 being compatible with Jira Data Center 9.4.0 - 9.17.4.

      Updating A4J to version 9.2.1 on Jira 9.12.X causes an error when a user tries to update an automation rule.

      Steps to Reproduce

      1. Install a vanilla instance of Jira Software Data Center.
        • This was validated with JSW DC 9.12.10 and 9.4.26.
        • This doesn't affect upgrading A4J to 9.2.1 on Jira version 9.17.X.
        • This doesn't affect Jira 10+.
      2. Create a new sample automation rule.
      3. Edit the sample rule.
        • Note no error occurs.
      4. Update A4J to version 9.2.1.
      5. Edit the sample rule.

      Expected Results

      The rule is updated without any errors on the UI nor on the application log.

      Actual Results

      An error is thrown on the UI as follows.

      An unknown error occurred. Please reload and try again.
      

      The UI shows a spinning wheel giving the impression the update failed.

      An error similar to the below is seen on the application log.

      2024-11-05 06:25:39,287-0600 http-nio-8080-exec-17 ERROR admin 385x663832x1 1vnu1k7 127.0.0.1 /rest/cb-automation/latest/project/GLOBAL/rule/1 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: com/atlassian/cache/ReadThroughCache
      java.lang.NoClassDefFoundError: com/atlassian/cache/ReadThroughCache
      	at com.codebarrel.jira.plugin.automation.service.ManualTriggerServiceImpl.ruleModified(ManualTriggerServiceImpl.java:245)
      	at com.codebarrel.jira.plugin.automation.event.EventRuleRegistryLauncher$2.onRuleChanged(EventRuleRegistryLauncher.java:87)
      	at com.codebarrel.automation.api.service.AutomationConfigServiceImpl.notifyChangeListenersRuleModified(AutomationConfigServiceImpl.java:566)
      	at com.codebarrel.automation.api.service.AutomationConfigServiceImpl.validateAndStore(AutomationConfigServiceImpl.java:559)
      	at com.codebarrel.automation.api.service.AutomationConfigServiceImpl.updateRule(AutomationConfigServiceImpl.java:322)
      	at com.codebarrel.jira.plugin.automation.rest.RuleResource.updateRule(RuleResource.java:254)
      	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
      

      Workaround

      Rollback the A4J upgrade to the previous stable version, by performing the steps below:

      • Go to Automation for Jira's Version history page and download A4J on a version lower than 9.2.1, for example 9.2.0
      • In the Jira application
        • Go to the page ⚙ > Manage Apps > Manage Apps
        • Look for the Automation For Jira app
        • Un-install it
        • Use the upload app button to install the A4J version downloaded from the version history page

            Assignee:
            Priyanka Jiandani (Inactive)
            Reporter:
            Thiago Masutti (Inactive)
            Votes:
            8 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: