Issue Summary

Using Assets import object mapping (see documentation for details), a conflict can occur with the Customer Service Management feature, when the attribute referenced in the AQL exists as a CSM field with the same name.

This has been observed only in scenarios when the schema name and/or object type name are also defined in the object mapping AQL.

Steps to Reproduce

Schema A

1. Create an Assets schema, call it Computers
2. Configure the schema to allow its objects to be referenced by other schemas
3. Create an object type within this schema, calling it Location
4. Create a default text attribute in this object type called City
5. Create an object and call it Dell with the City attribute set to Austin

Schema B

1. Create another schema calling it Devices
2. Create an object type and call it Desktop
3. Create an object type attribute calling it Area
   1. Select Object for the attribute type
   2. Select the Location object type from the *Computers schema for the type value
   3. Choose Reference for the additional value

Customer Service Management

1. Enable the CSM feature in a Jira Service Management project
2. Within the Organizations page click Manage Details
3. Select Manage detail fields
4. Create a simple text field called City

Import file

The following test file can be used:

name,location
Test,Austin

Import configuration

1. Within Schema B create an import configuration
2. Select CSV import and use the file created in the previous step as the source
3. Select the Desktop object type to map to
4. Create your field mapping
   1. Map name to Name
   2. Map location to Area
   3. Under AQL for the object mapping use the following AQL:

objectSchema = "Computers" and objectType = "Desktop" and "City" = ${location}

Expected Results

The import runs successfully and the object created links the Dell object from Schema A to the Area attribute.

Actual Results

While the objectSchema and objectType keywords are not necessary since the Area attribute is already configured for the relevant schema and object type, setting these when there is a Customer Service Management field with the same name causes the link not to break.

There are no errors in the import logs nor the application logs.

Workaround

Do not use the objectSchema or objectType keywords in the AQL mapping or rename either the field in the Customer Service Management feature or the attribute in Assets that is causing the conflict.