|
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, Philip,
I agree. I have created Thanks, 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 Hi,
We really need this functionality because International user have to use our JIRA for international projects. Thanks, 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 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... 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 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.
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) Hi Gerhard,
It is in fact possible to translate workflow transitions, although it is a fairly complicated. In order to do this:
Let us know if you need any more information. Thanks, 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 Hi,
custom event types should also be translateable. Cheers, Irene 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! We also require a better mechansim for transalting all customized workflows into different languages.
Thanks, 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 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 Hello everybody,
in our company are the same problems. It is unbelievable that the problem is known for more than 3 years, but even an unresolved problem. Kind regards, 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. 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, 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!! |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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