Issue Summary

The value changed trigger generates odd behaviour when evaluating smart values on issue creation, whereas on issue updated the behaviour is correct

Steps to Reproduce

The comment part of the rule proves to behave unexpectedly:
Priority was automatically changed to Minor
Reason: {{fieldChange.field}} was changed from {{fieldChange.fromString}} -> {{fieldchange.toString}} by {{initiator.displayName}}

1. When the execution is triggered by the creation of the issue (meaning when the issue is created), the comment added to the issue is malformed, unresolved comment:
   Priority was automatically changed to Minor
   Reason: customfield_14726 was changed from ** ->\ {self=https://<instance>/rest/api/2/customFieldOption/13113, value=1-Low, id=13113} by <username>
2. When the execution is triggered on the edition of the issue (meaning issue is already existing), the comment added by the execution of the rule works as expected:
   Priority was automatically changed to Minor
   Reason: Scope was changed from 5-High -> 1-Low

Expected Results

The fieldchange smart value to resolve correctly

Actual Results

The fieldchange smart value does not resolve correctly

Workaround

No workaround