-
Suggestion
-
Resolution: Unresolved
-
None
-
244
-
49
-
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Original description:
From the JIRA 3.2 Beta Release Notes:
"Continuing our commitment to a fully internationalisable issue manager, JIRA 3.2 provides the ability to translate all issue settings - i.e. Priorities, Statuses, Issue Types and Resolutions. This allows for even more complete translations to present JIRA to each user in their own chosen language."
I still miss being able to translate the following settings before JIRA is fully internationalisable.
1. Project Categories
2. Issue linking
3. Sub-Task Types
4. Workflows (i know i can make a new workflow in a second language, but when two persons with two different languages uses the same project, the workflow will only be presented in one of the languages) and their transitions.
5. Custom Fields (same problem as with workflows)
6. Security Levels
7. Field Sceen Tabs
8. Field descriptions
In other words: anything user configurable that is shown to the users.
As long as this is missing, it still gives no sense to use JIRA in a multilanguage environment. My setup is in danish. A person speaking only english will not be able to use it, since the workflow, the security levels and so on gives no meaning to him.
Disclaimer: i haven't installed 3.2 yet, so if any of the above settings actually IS translatable, please excuse me for not being up-to-date.
Regards,
Lars
- duplicates
-
JRASERVER-7509 localisation problems in Create Issue page
- Closed
- is duplicated by
-
JRASERVER-8183 untranslated strings in issue entry dialog
- Closed
-
JRASERVER-12702 renamed status remains
- Closed
-
JRASERVER-2614 Available Worklflow Actions not part of i18n
- Closed
-
JRASERVER-6841 workflow actions not translateable
- Closed
-
JRASERVER-10873 Multi language Support
- Closed
-
JRASERVER-12981 Projects in two differnent Languages
- Closed
-
JRASERVER-13723 Translate custom workflow transitions
- Closed
-
JRASERVER-14169 Translation of IssueLinking
- Closed
-
JRASERVER-17015 Add ability to translate (internationalise) custom workflow transitions (and possibly custom fields, statuses, etc...)
- Closed
-
JRASERVER-25580 Add translation feature for custom field.
- Closed
-
JRASERVER-33857 Translation of Custom Field - Values
- Closed
-
JRASERVER-71470 Translate Status Category
- Gathering Interest
- is incorporated by
-
JRASERVER-25418 Make announcement banner multilangual compliant
- Closed
- is related to
-
JRASERVER-7509 localisation problems in Create Issue page
- Closed
-
JRASERVER-11331 I18n with CustomField
- Closed
-
JRASERVER-63891 As a JIRA applications administrator, I would like to be able to translate fields and descriptions on the Field Configuration level
- Gathering Interest
-
JRASERVER-40049 Allow translation of custom field options
- Not Being Considered
- relates to
-
JRASERVER-2871 Are workflow-actions translatable?
- Closed
-
JRASERVER-6809 Show i18ned workflow transition names on view issue page
- Closed
-
JRASERVER-16421 Document which content can be internationalised to multiple languages and which can only be internationalised to a single language
- Closed
-
JRACLOUD-6798 Allow admins to translate items configurable in the administration section
- Gathering Interest
-
JRASERVER-31912 Add the ability to define the "jira.i18n.description" property in JIRA workflow transition
- Gathering Interest
-
JRASERVER-39850 Enable Application Link Issue Links Translation
- Gathering Interest
- was cloned as
-
JRASERVER-46029 Issue Linking description should be able to translate via multiple language pack.
- Gathering Impact
- links to
- 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...
-
Wiki Page Loading...