-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.1.2
-
7.01
-
9
-
Severity 3 - Minor
-
1
-
The name used for the field should be a canonical name in English to be consistent with JIRA's own system fields and so that the experience of choosing a field in the issue navigator in JQL mode is consistent and fields are only shown in one language when the user is entering or viewing a JQL query. Otherwise, situations like the one described at JRA-39009 happen.
JIRA Agile should provide translations for its own custom fields if available. Translations for custom fields is a supported feature since JIRA 6.0 and we should translate JIRA Agile custom fields via that mechanism.
- Discovered while testing
-
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
-
- Closed
-
- is duplicated by
-
JRASERVER-68004 Name of the created Custom Fields for Epic
- Closed
- is related to
-
JSWSERVER-11722 Eliminate language warnings about JIRA Agile fields
- Closed
-
JSWSERVER-10356 As a user in a global company I would like to have internationalisation of JIRA Agile custom fields
- Gathering Interest
-
SW-1601 Failed to load
- relates to
-
JSWSERVER-14833 Should be able to translate locked custom fields of JIRA Software
- Gathering Interest
[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
Support reference count | Original: 8 | New: 9 |
Remote Link | New: This issue links to "Page (Confluence)" [ 952346 ] |
Support reference count | Original: 7 | New: 8 |
Support reference count | Original: 6 | New: 7 |
UIS | Original: 2 | New: 1 |
UIS | Original: 4 | New: 2 |
UIS | Original: 2 | New: 4 |
Support reference count | Original: 5 | New: 6 |
UIS | Original: 1 | New: 2 |
Support reference count | Original: 4 | New: 5 |