-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
6.2.7
-
6.02
-
Symptoms
Using JQL, the fields you search for will use English names for all system fields, but translated names for all custom fields. For example when using Japanese and JIRA Agile, issuekey is in English, but sprint is in Japanese (スプリント):
This may cause confusion for users when typing JQL queries. It would be more consistent if they were all in the same language.
Steps to Reproduce
- Install a language pack
- Switch to using that language
- Install a plugin such as JIRA Agile, which has translated custom fields
- Try to search for system and custom fields using JQL
- is duplicated by
-
JRASERVER-59628 Custom Fields and Description are in Different Language to Specified JIRA Language
- Closed
- is related to
-
JRASERVER-11331 I18n with CustomField
- Closed
-
JRASERVER-39215 JQL can not use translated values for system fields
- Gathering Interest
- relates to
-
JRASERVER-39215 JQL can not use translated values for system fields
- Gathering Interest
- Testing discovered
-
JSWSERVER-10891 JIRA Agile should create custom fields (e.g. Epic Link) using a canonical name in English rather than a translation based on the server language
- Gathering Impact