-
Suggestion
-
Resolution: Unresolved
-
None
-
All versions
-
1
-
6
-
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
During JIRA Agile (GreenHopper) installation, the custom fields added are created in the default locale. Since JIRA supports I18N, it would be nice to have JIRA Agile to also support internationalisation.
Workaround
The field names and descriptions could be modified using the following steps:
- Unlock the locked field - How to unlock a Locked field
- Edit the field to the required label - Configuring a Custom Field
- Remember to again lock the unlocked fields to avoid modifications.
Note: The custom field names may also need to be updated to the new language text in other features like filter queries.
- is duplicated by
-
JSWSERVER-10361 Agile custom fields should automatically updated depending on JIRA Default Language
- Closed
-
JRASERVER-68004 Name of the created Custom Fields for Epic
- Closed
- is related to
-
JSWSERVER-11722 Eliminate language warnings about JIRA Agile fields
- Gathering Interest
-
SW-1601 Loading...
- relates to
-
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
-
JSWCLOUD-10356 As a user in a global company I would like to have internationalisation of JIRA Agile custom fields
- Closed
-
JSWSERVER-14833 Should be able to translate locked custom fields of JIRA Software
- Gathering Interest
- mentioned in
-
Page Loading...