Inconsistency around the overwriting of variables created in an automation rule

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 11.3.2, 10.3.16
    • Affects Version/s: 10.3.12, 11.2.0
    • Component/s: Actions, Fields
    • Severity 3 - Minor

      Issue Summary

      The customer has recently upgraded from Jira 10.3.11 to 10.3.12, after which they were no longer able to set an Automation for Jira variable to a new value which refers to the previous value of the same variable.

      Steps to Reproduce

      1. Create an automation rule with the following components:
        When: any trigger
        Then: Create variable testvariable with the value testvalue1
        And: Create variable testvariable with the value {{testvariable.replaceAll("testvalue1", "testvalue2")}}
        And: Add value to the audit log with the log message {{
        Unknown macro: {{testvariable}

        }}}

      1. Trigger the automation rule.
      1. Observe that in Jira 10.3.11, testvalue2 is logged, but in Jira 10.3.12, an empty string is logged.

      Expected Results

      In Jira 10.3.12, the updated value should be logged. 

      Actual Results

      In Jira 10.3.12, an empty string is logged.

      Workaround

      In the meantime the workaround will be to create the temporary variable to store the result

              Assignee:
              Benjamin Woodforde
              Reporter:
              Meenakshi Jha
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: