Issue Summary

For tenants that have thousand of Object types, having attributes referencing to other Objects may not display the expected results if the Object attribute has a similar name/pattern.

Steps to Reproduce

1. Create or update a schema, and add an Object type that has the Email attribute, which references another Object having this attribute as well.
2. In the Object type that has the Email attribute, create multiple Objects with a similar pattern (Add 25 or more Objects). For example
   1. mail1n@test.com
   2. mail2n@test.com
   3. .
   4. .
   5. .
   6. mail100n@test.com
3. Add an additional Email attribute with the following structure:
   1. n.test@test.com
4. Search the "n.test@test.com" text on the Object Type from step 1, in the Attribute that references the outbound Object that has the Email attribute (set as Label).

Expected Results

The value is displayed as expected.

Actual Results

The value isn't displayed, and instead, other value attributes with a similar pattern (“XXXXXn.XXXXX@test.com”) are displayed. This is because the attribute searcher appears to be using a LIKE AQL statement:

Email LIKE "n.XXXX@test.com" 

which matches the other Emails with a similar pattern.

Workaround

1. Bulk update Assets via CSV file. You can use the importer to implicitly enter the address that isn’t listed in the search attribute picker. We have the following documentation that covers this topic in detail: https://support.atlassian.com/jira/kb/how-to-update-the-existing-objects-using-the-csv-import-in-jsm-assets-cloud
2. Add an AQL filter to the Owner attribute within the Computers Object type.
   1. You can apply an AQL filter in the Owner attribute to only display the value you want to update.
   2. To do so, go to the Object type, click on the Attributes tab, and locate the attribute (For this example, the Email attribute), then click on the three-dot icon next to it. Click on the “Filter Objects” tab and add the AQL in question:

 Email = "n.XXXXX@test.XXX"

After adding the email to the Object, it'll be searchable. This can be reverted to list all the Email objects again. Perform the same action whenever you face this limitation.