Issue Summary

The Field value changed trigger generates odd behavior when evaluating the smart values fieldChange.toString on issue creation, whereas on issue updated, the behavior is correct.

Steps to Reproduce

1. Create a new custom field (for example, a select list field)
2. Create a new automation rule as follows:
   • Using the trigger Field value changed
   • Using the Log Action, print the following smart-vaue

     {{fieldChange.toString}}
     

Expected Results

The automation rule should print the value of the changed field.

Actual Results

Instead of getting the proper value, the smart value fieldChange.toString returns a full JSON payload:

{self=https://belkama.atlassian.net/rest/api/2/customFieldOption/10226, value=Generic Work, id=10226}

Workaround

Instead of using fieldChange.toString, using the issue.customfield_XXXXX smart value instead.

To get the ID of the custom field, go to ⚙ > Issues > Custom Fields, try to configure the custom field, and get the ID from the URL in the browser.