• Type: Bug
• Resolution: Won't Fix
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 6.2.7
• Component/s: JQL
• Labels:

  • affects-server
  • ho-jql-backend
  • i18n

1. 

   jql_field_translation.png

   4 kB

   06/Jul/2014 1:29 AM

[JRASERVER-39009] When using a language pack other than English, searching with JQL, system fields are all in English, custom fields are all in the other language

Collapse comment: Oswaldo Hernandez (Inactive) added a comment - 07/Jul/2014 5:08 AM, Edited by Oswaldo Hernandez - 07/Jul/2014 5:09 AM

Oswaldo Hernandez (Inactive) added a comment - 07/Jul/2014 5:08 AM - edited

Hi dmason,

I have spent some time today reproducing and attempting to understand this behaviour, and ultimately this is actually a JIRA Agile problem

In further detail, the jql view allows to refer to a field by either its name (system fields) / name or id (custom fields). It's not possible to refer to a field by its translated name only by its canonical name

Now, JIRA Agile's custom fields seem to support this because the plugin is smart and it tries to pick a canonical name for the field that matches the server language at the moment that JIRA Agile is installed.

So for instance, if a user with English as his preferred language would login to an instance where the server language is set to Japanese, they would have to create their jql queries using japanese field names for JIRA Agile fields. This is clearly undesirable behaviour and I will raise a bug in the JIRA Agile project to track this.

In the future, it might prove useful to improve JIRA such that users would be able to input and view JQL queries using the translated name of fields, and be able to share these with others / etc... no matter what their preferred language is. That would fall in the territory of a feature request.

Hope the information here clarifies things.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Expand comment: Oswaldo Hernandez (Inactive) added a comment - 07/Jul/2014 5:08 AM, Edited by Oswaldo Hernandez - 07/Jul/2014 5:09 AM

Oswaldo Hernandez (Inactive) added a comment - 07/Jul/2014 5:08 AM - edited Hi dmason , I have spent some time today reproducing and attempting to understand this behaviour, and ultimately this is actually a JIRA Agile problem In further detail, the jql view allows to refer to a field by either its name (system fields) / name or id (custom fields). It's not possible to refer to a field by its translated name only by its canonical name Now, JIRA Agile's custom fields seem to support this because the plugin is smart and it tries to pick a canonical name for the field that matches the server language at the moment that JIRA Agile is installed. So for instance, if a user with English as his preferred language would login to an instance where the server language is set to Japanese, they would have to create their jql queries using japanese field names for JIRA Agile fields. This is clearly undesirable behaviour and I will raise a bug in the JIRA Agile project to track this. In the future, it might prove useful to improve JIRA such that users would be able to input and view JQL queries using the translated name of fields, and be able to share these with others / etc... no matter what their preferred language is. That would fall in the territory of a feature request. Hope the information here clarifies things. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .