Issue Summary

When using Jira Automation to track field changes for the Components field, if the Components field is updated with multiple components in a single edit, the rule only evaluates the first added component. The smart values {{fieldChange.fromString}}, {{fieldChange.toString}}, {{addedfieldChange.values}}, and {{deletedFieldChange.values}} do not return the full set of changed values and instead only contain the first entered component.

Steps to Reproduce

1. Create or edit an automation rule that uses the Field value changed trigger on the Components field.
2. In the rule, log or use the following smart values in an action (e.g., Log action or Comment):

   • {{fieldChange.fromString}}

• • {fieldChange.toString}}

• • {{addedfieldChange.values}}

• • {{deletedFieldChange.values}}

1. In an issue where the rule applies, edit the Components field and, in a single edit operation, select multiple components at once (for example: Component1, Component2, and Component3) and save the change.
2. Check the automation audit log and/or the resulting action output for the smart values listed above.

Expected Results

• The automation rule should correctly evaluate the full change to the Components field, even when multiple components are added or removed in a single edit.
• The following smart values should contain all relevant values, as per the documentation:
  • {{fieldChange.fromString}} should list all previous components.
  • {{fieldChange.toString}} should list all new components after the change.
  • {{addedfieldChange.values}} should list all components that were added in that change (e.g., Component1, Component2, Component3).
  • {deletedFieldChange.values}} should list all components that were removed in that change, if any.

Actual Results

The automation rule triggers only once for the multi-value update, but the field-change-related smart values only contain the first added component. 

This behavior contradicts the documented expectation that {{addedfieldChange.values}} and related smart values return all values that the field was changed to or from, as described in the public documentation:
Automation smart values - issues

Loom video has been recorded to display the issue: https://www.loom.com/share/7b21ec9c81bd469db425d04e5f3fce77

Workaround

At the moment, the only partial workaround is to avoid updating the Components field with multiple components in a single edit operation. Users need to add or remove components one at a time so that automation rules with conditions based on added component values can evaluate and execute the expected actions for each change.