As part of this investigation (AUTO-1258) we realised that when Smart Values print out an Optional by itself, we coerce it to its nested data type, so correctly print that out, but lists of Optionals do not coerce the elements's properties, so we try to print the Optional data type in that case, which is an empty string. We believe this is a legitimate suggestion/feature improvement and raised a tracker for it here.

Steps to reproduce:

1. Create a field that contains a list of Optionals, for example
   1. In JSM create another field of Assets objects type and add it to a screen.
   2. Create an issue and add a value to the new custom field (select any object available).
2. Create an Automation rule to print the values of the above field.
3. Log action with smart value 
   issue.customfield_XXXXX.Name
   1. Here, XXXXX represents the ID of the custom field just created
   2. issue.customfield_XXXXX is representing a list of Optionals (with only one element because the field type is Assets objects)
   3. 'Name' is a property inside the Optional in the list that could have any value (e.g. 'Demo Service')
4. Currently the output is empty string instead of the values of the 'Name' properties of the Optionals inside the list (e.g. 'Demo Service')
5. Expected output: the value of 'Name' property inside the Optionals from the list (e.g. 'Demo Service' if there is a list with only one Optional)

This will help Automation customers debug smart values of lists of optionals with properties.