-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
4.20.1, 4.21.1
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
IQL with Placeholder doesn't work when custom field name is used with Translation enabled.
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Create 2 Insight Custom field: InsightCF01 and InsightCF02.
- InsightCF01 will be used as Placeholder in InsightCF02
InsightCF01: IQL: objectType = Country InsightCF02: IQL: "Country" = ${InsightCF01}
- Add translate to InsightCF01 for different Language from (Settings --> Issues --> Custom field --> Translate --> add a Language: Ensligh (UK))
Expected Results
IQL should work irrespective of the Profile Language
Actual Results
Login as User with default Language set and IQL works Login as User with traslated Language set and IQL doesn't work
Workaround
User "customfieldid_<customfieldid>" in place of the "custom field name" in IQL Placeholder.
- is related to
-
JSDSERVER-7830 Customfield Placeholder to support CF translations as well
- Gathering Interest