The {{fieldChange}} smart value properties does not work.

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 7.4.2
    • Component/s: Smart-values
    • Severity 3 - Minor
    • 2

      Issue Summary

      The following {{fieldChange}} smart values properties do not return any values when used in the rule as described in this document

      {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value.

      {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value.

      {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value.

      {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted.

      {{deletedFieldChanged.values}} - Returns the value/values deleted.

      This is reproducible on Cloud: Yes

      Steps to Reproduce

      1. Create a rule to trigger when a field value is changed for the Fix versions field.
      2. In the automation rule, use the following smart values to add the values in the audit log:

        {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value.

        {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value.

        {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value.

        {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted.

        {{deletedFieldChanged.values}} - Returns the value/values deleted.

      3. Then execute the rule by changing the value for the Fix version field.

      Expected Results

      The Audit log action in the rule should capture values as defined in the property definitions.

      Actual Results

      These {{fieldChange}} smart values properties do not return any values.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Daniel Ramotowski (Inactive)
            Reporter:
            Shashank Sreedhar
            Votes:
            14 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: