Issue Summary

When importing CSV data, fields of the type Asset referenced object fail with the Could not find Assets object/s error if the asset name is used in the CSV.
If using the admin version (external system import), the value is not added. If using the issue bulk create option, the issues are not created.

Steps to Reproduce

1. Create an Asset schema from the "Sample IT Asset Schema" template
2. Create an asset of the Host type "host 1"
3. Create an asset of the Connected Device type "device 1", with "host 1" as its host
4. Create an "Assets object" custom field called "Host", with the AQL objectType="Host"
5. Create an "Assets referenced object" custom field called "Device", referencing the previous field, configured for inbound references, and AQL objectType="Connected Device"
6. Validate that adding the "host 1" and "device 1" to an issue works as expected
7. Import this CSV, replacing the object keys as appropriate:

   Summary,Type,Host,Device
   new issue,Task,host 1,device 1
   new issue 2,Task,host 1,IA-4
   new issue 3,Task,IA-3,IA-4
   

Expected Results

Three new issues are created.

Actual Results

If using the Bulk Create feature, two new issues are created.
The first line fails with the error:

Issue can't be created due to the error/s [ Could not find Assets object/s (device 1) ]

If using the External system import feature, it creates all three issues, but the first one doesn't have the "device" field set.
This warning is shown:

Cannot add value [ [device 1] ] to CustomField Device in Issue with summary 'new issue'. Probably value was in incorrect format.

Workaround

When importing asset referenced fields, use the object key instead of its name.
If in doubt, always use the key to avoid errors.