-
Suggestion
-
Resolution: Unresolved
-
1,330
-
98
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
With Jira 6/JRA-11331, we have the possibility to translate custom fields, which is great.
But we are still missing the possibility to translate custom field options. E.g. if you have a custom field of type select list, you can now translate the custom field name, but not the different values in that list. This is a big shortcoming.
- is duplicated by
-
JRACLOUD-92676 Translate field names and option which shown in English
- Closed
- is related to
-
JRACLOUD-78930 Improve translation of default Resolution options (German - Germany)
-
- Closed
-
-
JRACLOUD-92676 Translate field names and option which shown in English
- Closed
-
JRASERVER-40049 Allow translation of custom field options
- Not Being Considered
- relates to
-
JRACLOUD-11331 I18n with CustomField
- Closed
-
JRACLOUD-63891 As a JIRA applications administrator, I would like to be able to translate fields and descriptions on the Field Configuration level
- Closed
-
JRACLOUD-6798 Allow admins to translate items configurable in the administration section
- Gathering Interest
-
JRACLOUD-83145 Should be able to translate locked system and custom fields in Jira
- Gathering Interest
- blocks
-
ACE-2357 Loading...
- is addressed by
-
ENT-2293 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[JRACLOUD-40049] Allow translation of custom field options
Support reference count | Original: 97 | New: 98 |
UIS | Original: 1429 | New: 1330 |
UIS | Original: 1466 | New: 1429 |
UIS | Original: 1465 | New: 1466 |
UIS | Original: 1448 | New: 1465 |
UIS | Original: 1490 | New: 1448 |
UIS | Original: 1424 | New: 1490 |
UIS | Original: 1444 | New: 1424 |
UIS | Original: 1426 | New: 1444 |
This should have been an option from the begining. Pausing/postponing it makes no sense when there are many people just waiting and asking for this to be provided. I don't understand why the need to reflect, when all the requests on here clearly show the need of this feature. Being able to translate custom fields is a must.