Adding fields to Clone Issue or Create Issue action of Automation Rule clears the values set for other fields

XMLWordPrintable

    • Severity 2 - Major
    • Jira Service Management

      Issue Summary

      While editing Clone Issue or Create Issue action of your Automation Rule, adding a field from the drop down menu will clear the values set for other fields.

      Refer to the attached screen recording where the field reset is captured and the HAR file (atl-grao-tst.atlassian.net.har) captured for the operation. HAR file shows a batch update being performed when a new field is added or removed from the dropdown.

      Tested on Cloud only.

      Steps to Reproduce

      1. Ensure that you have an automation rule which clones tickets using the Clone Issue action. Go to Clone Issue action under your automation rule
      2. Add an additional field to be selected from the drop down.
      3. On selection of the field, all the existing fields are cleared

      Expected Results

      Only the newly added field should not contain default value or no value. All the other fields which were set earlier should be intact.

      Actual Results

      All the fields are reset to default values.

      Workaround

      • Although adding a field from the drop down menu clears the values already set, you can re-add the values manually.
        OR
      • Use the Advanced field editing in Automation Rule to set the values, which doesn't seem to be impacted.

        1. CloneIssue.jpg
          71 kB
          Gautham
        2. CloneIssue_Reset.jpg
          85 kB
          Gautham
        3. CloneIssue_Add.jpg
          82 kB
          Gautham

              Assignee:
              Unassigned
              Reporter:
              Gautham (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: