IQL with Placeholder doesn't work when Custom field translate is used

XMLWordPrintable

    • Type: Bug
    • Resolution: Not a bug
    • Priority: Low
    • None
    • Affects Version/s: 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

      1. Create 2 Insight Custom field: InsightCF01 and InsightCF02.
      2. InsightCF01 will be used as Placeholder in InsightCF02
        InsightCF01: 
        IQL: objectType = Country
        
        InsightCF02:
        IQL: "Country" = ${InsightCF01}
        
      3. 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.

        1. STR.mov
          26.91 MB
          Shreekesh Mohan

              Assignee:
              Unassigned
              Reporter:
              Shreekesh Mohan
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: