Using a translated Insight custom field in a JQL filter using iqlFunction() returns no results

Issue Summary

Using a translated Insight custom field in a JQL filter using iqlFunction() returns no results

Steps to Reproduce

1. Have an Insight Object custom field
2. Translate this field into another language, for example Czech
3. Specify user language preference to the translated language
4. Search for issues with a JQL filter including that translated field and an iqlFunction(), for example:

project = ABCD and issuetype = "Task" and "My Translated Insight Custom Field" in iqlFunction("anyAttribute = potato")

Expected Results

Search results are displayed

Actual Results

Search results are not displayed. However, if user language is changed back to English, results are displayed.

Workaround

Use the ID of the custom field instead of the field name in the JQL filter. For example customfield_12345. Note that this is only a partial workaround and creates an administrative burden, as non-admin users will not be able to identify the field ID without admin assistance.