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

JQL can not use translated values for system fields

XMLWordPrintable

    • 2
    • 6
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Situation

      Issue statuses in Basic Search in the Issue Navigator can only be found by the translation of the language pack used by the current user. The same status in the Advanced search (or JQL), can only be found by the original value.

      Steps to reproduce

      1. Set the Default language of JIRA to English
      2. Set the user language of JIRA to Dutch
      3. Create a status "Deleted"
      4. Through the Translate statuses option, add a translation to Dutch "Verwijderd"
      5. Generate issues in status "Verwijderd"

      Expected result

      When searching for issues through the Advanced Search in the issue navigator (or other searches using JQL) in status "Verwijderd", the previously generated issues will be found

      Actual result

      No issues can be found in status "Verwijderd". However issues can be found in status "Deleted

          Form Name

            [JRASERVER-39215] JQL can not use translated values for system fields

            Christian S added a comment -

            4ba2600351f9 thanks for that workaround,

            we having quite huge issues by searching tickets with in aqlfunction on profiles != english

            this needs to be fixed (as many other thinks to get into daily work)

            Christian S added a comment - 4ba2600351f9 thanks for that workaround, we having quite huge issues by searching tickets with in aqlfunction on profiles != english this needs to be fixed (as many other thinks to get into daily work)

            Pawel added a comment - - edited

            Problem with Field name in aqlFunction("zzz = true")
            the solution is cf[id] in aqlFunction("zzz = true")
            use CF.
            but it doesn't solve our problem, it's just a workaround.

            Pawel added a comment - - edited Problem with Field name in aqlFunction("zzz = true") the solution is cf [id] in aqlFunction("zzz = true") use CF. but it doesn't solve our problem, it's just a workaround.

            Tomáš Smolák added a comment -

            +1

            Tomáš Smolák added a comment - +1

            Arnold Godin added a comment -

            Do you have an update please? We are using gadget with predfined JQL like the Sprint Health Gadget and it is quite problematic when you are using a translation of Flagged field for exemple ...

            Arnold Godin added a comment - Do you have an update please? We are using gadget with predfined JQL like the Sprint Health Gadget and it is quite problematic when you are using a translation of Flagged field for exemple ...

            Pujan Ziaie added a comment -

            How difficult is resolving this from the development point of view? And what is the impact?

            Pujan Ziaie added a comment - How difficult is resolving this from the development point of view? And what is the impact?

            Antoine Ferron added a comment -

            Hi,

             

            It seems like the correspondance between the fields in English and the field in french is broken.
            Some are using CF, Some Plugin (Xray fields in the screenshots) and other not (fields summary, status...)

             

            A bug to fix please !!

            Antoine

            Antoine Ferron added a comment - Hi,   It seems like the correspondance between the fields in English and the field in french is broken. Some are using CF, Some Plugin (Xray fields in the screenshots) and other not (fields summary, status...)   A bug to fix please !! Antoine

            Ląd Maciej - PZU added a comment -

            It is a big BUG. 

            Ląd Maciej - PZU added a comment - It is a big BUG. 

            Chris L added a comment -

            Agreed.  Still a bug for us!  In our case in JIRA Service Desk, we are using End User for Reporter in the language pack.  Now we cannot search for End User in JQL.

            Chris L added a comment - Agreed.  Still a bug for us!  In our case in JIRA Service Desk, we are using End User for Reporter in the language pack.  Now we cannot search for End User in JQL.

            Nicolae Gherman added a comment -

            still a bug in JIRA 7.0.2

            Nicolae Gherman added a comment - still a bug in JIRA 7.0.2

            Manuel Arranz added a comment - - edited

            8 months and still no changes with this issue? Does "Don't f... the Customer" really mean "Don't f... the English Speaker Customer" ? If basic functionality like Search does not work for translated custom fields it does not work at all (and it is not a Suggestion, it is a bug)

            Manuel Arranz added a comment - - edited 8 months and still no changes with this issue? Does "Don't f... the Customer" really mean "Don't f... the English Speaker Customer" ? If basic functionality like Search does not work for translated custom fields it does not work at all (and it is not a Suggestion, it is a bug)

            Manuel Arranz added a comment - - edited

            Hi,

            I don't understand why is this moved from bug to suggestion. If the status shown to the user is different from what he sees in the issue, how can he know what he is looking for?

            If jira provides the possibility to translate status (and it does), translations should be used everywhere, not canonical values. Right now it seems to be used randomly in the application which makes it utterly unusable.

            Manuel Arranz added a comment - - edited Hi, I don't understand why is this moved from bug to suggestion. If the status shown to the user is different from what he sees in the issue, how can he know what he is looking for? If jira provides the possibility to translate status (and it does), translations should be used everywhere, not canonical values. Right now it seems to be used randomly in the application which makes it utterly unusable.

            Stanislav Dashkovsky added a comment -

            Agree with marranzr. Users cannot use search.

            Stanislav Dashkovsky added a comment - Agree with marranzr . Users cannot use search.

            Manuel Arranz added a comment -

            Disagree with priority. This bug makes Advanced JQL unusable because users don't know what status or custom field they are asking for.

            Best Regards

            Manuel Arranz added a comment - Disagree with priority. This bug makes Advanced JQL unusable because users don't know what status or custom field they are asking for. Best Regards

            Manuel Arranz added a comment -

            The same happens with Custom Field Translations.

            We have found this problem not just in Advanced JQL. The same happens with:
            History tab
            Workflow Editor

            Manuel Arranz added a comment - The same happens with Custom Field Translations. We have found this problem not just in Advanced JQL. The same happens with: History tab Workflow Editor

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Votes:
              95 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated: