Issue Details (XML | Word | Printable)

Key: JRA-6798
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Lars
Votes: 54
Watchers: 29
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Allow admins to translate items configurable in the administration section

Created: 26/May/05 01:29 PM   Updated: 28/Oct/08 03:48 AM
Component/s: Internationalisation
Affects Version/s: 3.2 Beta
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference

Participants: aborrull, Andreas Kuhrt, Andreas Weibel, Ann-Sophie HOCQ, Anton Mazkovoi [Atlassian], Berta Setien, Brian Nguyen [OLD], Christoph Henrici, Dylan Etkin [Atlassian], Gerhard, Ina, Kai Irene Busch, Lars, Marco Kundert, Mel Belacel, Moises Delgado, Philip Herbst, pierre-yves voirol, René Spengler , Samuel Drillaud and sensui
Since last comment: 5 weeks, 1 day ago
Support reference count: 10
Labels:


 Description  « Hide
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 projekt, the workflow will only be presented in one of the languages)
5. Custom Fields (same problem as with workflows)
6. Security Levels
7. Field Sceen Tabs
8. Field descriptions

In other words: anything unser 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



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Philip Herbst added a comment - 26/May/05 01:52 PM
I completly agree with Lars
What I dont get about i18n is that some workflow steps have corresponding properties defined in XML which are shown in some screens, e.g. resolve or close(submit button). But they aren't shown in view Issue Screen at available workflow steps...IMHO they should appear in every screen or nowhere.

Cheers,

Philip


Lars added a comment - 26/May/05 02:17 PM
And by the way... as mentioned many times before... e-mail.

Why are they still not translatable?


Anton Mazkovoi [Atlassian] added a comment - 26/May/05 11:46 PM
Lars,

You are absolutely right. It is not possible to translate the items you have mentioned in JIRA 3.2 to different languages. We are taking the translation one step at a time, and hopefully, in the future any name/description/string that is created in the admin section and is shown in the user land will be internationalisable.

Thank you for providing a comprehensive list of items.

Regarding e-mail: untortunately we have not had the time to address this issue for JIRA 3.2. We have quite a large number of feature requests, and we can only implement a few at a time.

Thanks,
Anton


Anton Mazkovoi [Atlassian] added a comment - 27/May/05 02:04 AM
Philip,

I agree. I have created JRA-6809 to track progress on this.

Thanks,
Anton


Marco Kundert added a comment - 15/Sep/05 04:45 AM
I'm also realy not happy with this situation. I agree with lars! And I cannot understand, why Atlassian calls it's JIRA internationalisable!!!
The system is still unusable in multilanguage enviroments. If Atlassian realy want's to sell a multilanguage system, this issue should have one of the highiest priority.
I cannot understand, why other customers do not run into the same problems (only 3 Votes on this issue)

Marco


Ann-Sophie HOCQ added a comment - 19/Jan/06 03:32 AM
Hi,
We really need this functionality because International user have to use our JIRA for international projects.
Thanks,

pierre-yves voirol added a comment - 22/Feb/06 01:07 AM
Not very happy with this situation.

Some employees of my company speak german, some employees doesn't speek englisch very well (they speak french).

So we must be able to translate all "customisable" parts of JIRA.

Thanks


Lars added a comment - 22/Feb/06 03:15 AM
It would be great, if you would consider a fix version for this.

I wonder why you start implementing such great functionality in 3.2 and then stops there. I would expect 3.3 to include the rest of the missing parts. Now were looking at an upcoming 3.6, and this version still misses them.

Were also still missing i18n'ed e-mails... the rest of JIRA has been multilanguage for a hundred years...


Dylan Etkin [Atlassian] added a comment - 22/Feb/06 07:38 PM
Hi Lars,
We did i18n the admin section in 3.5, but we have not addressed the dynamic elements that are mentioned in this issue. If you would like to read more about how we decide which features will go into a release you can read about it here.
Thanks,
Dylan

aborrull added a comment - 20/Mar/06 09:42 AM
We're having the same problem (Jira 3.5.1), several users from several countries are using the same project and several items are not translated. We're using English as default language in order to minimize the problem, but it's not really the best way.

Gerhard added a comment - 29/Jun/06 03:43 AM
we have created several filters which are globally available; example for names: "my all to be closed", "my all info requested". These filters are being used for portlets in the default dasshboard

if a user is logged in who has another language in his profile than english, he will still see the name of the filter as defined - I did not find a place where I can translate the filter name

the same is the case with workflow activities: we have defined "provide info" or "confirm test" - again, I did not fin a place where I could translate them to all other languages we would need (german, french, italian, spanish)


Brian Nguyen [OLD] added a comment - 29/Jun/06 09:27 PM
Hi Gerhard,

It is in fact possible to translate workflow transitions, although it is a fairly complicated.

In order to do this:

  1. Open the jar file atlassian-jira/WEB-INF/lib/language_<language code>_<country code>.jar
  2. In that jar edit the file \com\atlassian\jira\web\action\JiraWebActionSupport_<language code>_<country code>.properties
  3. Add the translation to the file, for example:
    provideinfo.title = This is a test translation
  4. Make sure you remember the key you used. Save the file.
  5. Restart Jira
  6. Goto your workflow in Jira (Administration -> Global Settings -> Workflow)
  7. Click on the transition you would like to translate
  8. Click on View properties of this transition
  9. Add the property:
    • Key = jira.i18n.title
    • Value = <key of the translation>
  10. Activate the workflow
  11. Repeat steps for each transition and language

Let us know if you need any more information.

Thanks,
Brian


Mel Belacel added a comment - 13/Nov/06 07:52 AM
The lack of ability to translate custom fields is very frustrating especially if you manage to translate nearly everything for your users (dashboard etc) but end up having some of the most important fields (custom fields) in English when the users are French.

An update on this would be appreciated

MB


Kai Irene Busch added a comment - 03/Sep/07 06:33 AM - edited
Hi,

custom event types should also be translateable.

Cheers, Irene


Moises Delgado added a comment - 14/Dec/07 04:19 PM
JIRA is so useful that we use it around the world. So, We need to translate some words for our users in another language. Please fix this Improvement.

Thanks!
Cheers


René Spengler added a comment - 20/Feb/08 12:39 AM
We also require a better mechansim for transalting all customized workflows into different languages.

Thanks,
René


sensui added a comment - 23/Jul/08 02:32 AM
I'm glad to be able to translate workflow transitions by edit the properties file.
But I still have problem to translate custom fields, hope there'll be a resolution soon.

Samuel Drillaud added a comment - 24/Jul/08 08:56 AM
Hi,
like sensui, I have translated the workflows transitions by the properties file and this translation is OK. But I have a problem with the tag's button of the screen transition. Indeed the button is not translated in English and it has always the french term of my transition for a profile using english language.

Is it possible to translate the tag's button with the properties file or another means ?

thanks for yours answers

Sam


Andreas Kuhrt added a comment - 29/Jul/08 11:17 AM
Hi,

we also have the same problem. Most of our colleagues speak german, so our custom fields are in german. Now we need to include our american colleagues into JIRA. If they want to fill out a form, they do not understand it.

So please make it possible to translate custom-fields.

thx

Andreas

using JIRA Enterprise Edition, Version: 3.12.1-#299


Ina added a comment - 07/Aug/08 07:49 AM
Hello everybody,

in our company are the same problems.
The translation of items in all language property files is very laborious, and it doesn't offer the possibility to translate all parts of jira, e.g. the buttons on the screens.

It is unbelievable that the problem is known for more than 3 years, but even an unresolved problem.
When will the problem be fixed? Or at least a part of it (and which one)?

Kind regards,
Ina


Christoph Henrici added a comment - 17/Sep/08 10:16 AM
I am slightly astonished that this item is still open, unassigned and unscheduled. We are a Swiss Company and are accustomed to support at least 3 languages. It really cant be that internationalization stops with adaptability and customizability, in contrary. Workflow and Customs really should support i18n. What should be explain are Italian or French speaking colleagues? Oh, we have this great new Issue Tracking Software..... but hmm yessssss our Custom Fields are in German.....

Looking forward to a schedule and assigment of this issue.
Thx Christoph


Andreas Weibel added a comment - 03/Oct/08 08:40 AM
Hi,

We have the same problem... We are a Swiss company, as well. Some of our users are German-speaking, some French-speaking, some Italian-speaking... It would be great if we could translate at least the Custom Field names.

It would be great if this issue could be resolved in one of the next releases of Jira.

Thanks,
Andreas


Berta Setien added a comment - 28/Oct/08 03:48 AM
hi all!!
We also need this. We are a Spanish company and we have users from many countries. So far we did the work around by having everything in the languages most used but it´s a pain when it comes to read reports or issues for project managers or people who only speaks one language.

WE really, really like this to be done.

Thanks for all!!