Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-68950

"Version Picker" type custom field link is not working when field is translated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 7.11.1, 7.12.0
    • Custom fields, Translations

    Description

      Summary

      When user translated "Version Picker" type custom field to "Translate Custom Version" and click version number on the issue, search feature is not working properly due to "Field 'Translate Custom Version' does not exist or you do not have permission to view it." error.

      Steps to Reproduce

      1. Create Custom field "Custom Version" with "Version Picker (multiple or single)" type
      2. Translate custom field (ex. Translate Custom Version)
      3. Add value to "Translate Custom Version" field on a issue
      4. Click version number which is placed "Translate Custom Version" field

      Expected Results

      JQL should be below.

      • project="TP" AND "Custom Version"="Version 2.0" ORDER BY priority ASC
      • project="TP" AND cf[xxxx]="Version 2.0" ORDER BY priority ASC

      Actual Results

      JQL use below query and return "Field 'Translate Custom Version' does not exist or you do not have permission to view it." error

      • project="TP" AND "Translate Custom Version"="Version 2.0" ORDER BY priority ASC

      Workaround

      Change translated field name to initial custom field name on JQL manually.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tsuzuki@atlassian.com Tomoko Suzuki
            Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated: