Insight/Asset import object mapping enforcing case sensitive for multiple objects

[Claire Berry]

Hi, I have a CSV import that looks something like this:

And I am importing a Distribution List object into Insight with this CSV file. 

There is another User object which I am trying to map the Members to.

There is an attribute which links to the other User object:

And this object cardinality is set to 'Unlimited'.

In the Object Mapping (AQL) of the import, I am mapping the Members data locator from the CSV file to the Members attribute with the following mapping:
Email IN (${Members${0}})
Where 'Email' is the name of the attribute on the Okta User object that matches the values in the Members column of the CSV file. 

What I have found is that when mapping multiple values like this, it seems to enforce a case sensitive check. It works fine and ignores the case when mapping just on 1, for example with: Email = ${Member}

When I test searching the IQL/AQL in Jira to search for these emails:
"Email" IN ("john.doe@company.com","Jean.Smith@company.com")

I get the 2 users. Even though, John Doe's email is with capital letters: John.Doe@company.com.

But when using the multiple value place holder, is seems to only find Jean Smith's account when mapping the email, as her email address case matches the Okta user: Jean.Smith@company.com

Is anyone aware of this bug? Or know is there anything that can be added into the multiple value placeholder to ignore the case?
https://confluence.atlassian.com/servicemanagementserver/2-create-object-type-and-attribute-mapping-1044784497.html#:~:text=Name%20IN%20(%24%7BDATA%20LOCATOR%24%7B0%7D%7D)