Will the Language Support option in project settings be added to the Server Version and not just the Cloud version? 

Hi Jira Service Desk Team,

we would love to see the survey https://jsd-beta.typeform.com/to/VS5QKT. Can you please make it public? Thanks in advance. Regards, Andrea

Is this also for hosted JIRA Service Desk availible?

https://confluence.atlassian.com/servicedeskcloud/translating-your-customer-portal-and-supporting-multiple-languages-886180551.html

I think this is what we all need.

It would be a good feature to allow the language packs to be used in JIRA Cloud as well as on-premise Jira.

Hi all,

Thanks for all your comments. There's certainly a lot of interest behind this feature!

We would love to hear more from you on how your team shall add and maintain multiple languages on the portal. Understanding this will help us make the right thing that fits your needs perfectly.

If you would like to help out, please take 2 minutes to answer these questions - https://jsd-beta.typeform.com/to/VS5QKT.

Cheers,
JIRA Service Desk Team

Would really love to see this added. We need many many languages to make JSD a viable enterprise option.

Hi guys, any news about this issue?

We are having many troubles with this issue, for our users is not a problem use JIRA in english, but for our customer is a big problem to view the labels in english, we really need this in portuguese-BR, at least the portal and e-mail communications! It is causing a bad impression about atlassian products.
Do you have a due date?

We need to be able to translate the customer portal in the customer language. This is very important for us !
We are using the cloud version.

For global use of ServiceDesk for international customer base it is mandatory to have full localized of the customer frontend.
TransWare AG

Hi,
The only way to translate dynamic text in Customer Portal is to use tool for creating language versions, inside our plugin. You can see how simple it is in the documentation: http://plugins.intenso.pl/display/PLUG/Service+Pack+for+JIRA+Service+Desk . Displaying the flag is unnecessary because the plugin takes the language setting from the user's profile.

Piotr Mazij
InTENSO
Application Support Engineer

Hi,

We are a Swiss Company and would like to have the option to allow for English, German and French on the customer Portal. (Small Icon to select from on the top rigtht of the page or something similar)

Can you please let me know the best way to set this up?

Hi,
We are supporting multilanguage support for non static text in our plugin for JSD. Feel free to try it.
https://marketplace.atlassian.com/plugins/com.intenso.jira.plugins.jsd-extender

einkauf10 - This is currently not a planned roadmap iterm.

In general Atlassian does not publish its roadmaps because of the expectations it sets and the disappointment when things do not go to plan.

However we do use JAC and other resources to gauge interest and shape the work we do so please outline your requirements if you have specific needs.

Is there a current information as to whether and when a multi-language support is to be introduced?

Thanks Brad for the quick reply.
The "non static" texts are also the texts I was referring to. This is what we liked about JCD, that one can easily adapt the Jira field texts into something the customer understands better.

In my use case, I as admin, would do both, the set-up in English and the translation of the fields into German.
My intuitive way of doning that was, I just logged on in German and "translated" the self defined texts. Later I found out that I just changed the text but not translated them. So for me it would be sufficient if I could just change my language and then translate the texts. A Little Icon next to the custmized text that indicates if the original language is shown or if the text is already translated into the logon language would help.
If one has to administer many more languages this would probalbly be not the best way. some sort of Translation console would be better and the user would probably be an "translator" rather than an admin.
Hope that helps and we will soon get a possability to translate the text one way or the other.

Regards,
Markus

markus.pogrzeba

The latest released version of Service Desk 1.1 has German translations for all the ServiceDesk static text. Please try it out.

This issue here is more about all the "customer defined" non static text. For example you can create your own named request types and field descriptions etc... You as a German speaker would create them in German but what if you had Polish customers? How would that Polish customer see the Request Type name and would it be translated by you are the administrator at configuration creation time?

This is the "non static" text that we are talking about in this issue

Cheers
Brad Baker
Service Desk Architect

Hello,
we've just installed the JSD and I am very happy how quickly I was able to set up a customer portal. Once I wanted to translate the portal into German I was very disappointed to find out that it's not possible yet. As Jira supports already multiple languages including German the users will not understand why for one part of Jira suddenly only one language is supported.
We are a multilingual company (currently German and English) and need to provide the customer portal also in those languages.
My expectation was that Jira Service Desk supports the same languages than Jira and has the flexability to support those languages also for the texts we create when setting the customer portal.

I have updated the title of this feature request because the original "Multilanguage support" is a little to narrow.

The Service Desk dev team plans to add I18n support for its static text, that is all the text that is produced by the software in property files and it will target the usual large market languages such as German and French. Will will also use translations.atlassian.com to allow other parties to produce other translations of the static text.

But what is being asked for in this feature request is something more specific. And that is translation of dynamic text entered by Service Desk agents.

The challenge here is that the existing static I18n features don't offer a good solution to this problem because its "local" to each Service Desk instance and indeed per Request Type.

This is by no means impossible to do (as its just a simple matter of programming ) but it will be a lot more work for the software and indeed the local administrators of Service Desk.

Hello Brad,
On our side, two languages in Customer Portal would be enough. But this should not mean that some other company needs more languages.
I agree with you about the user experience. I believe, administrators could inject the translated strings. Of course easier the better. For example using a language pack for the translations would make the process much more easier rather than entering the translated strings via a UI one by one.

For our company 2 languages would be enough, because people with minor language can easily fulfill request on English.
It's not a big deal for us to make a two versions of visible name/description of fields which will go to the Customer Portal, but the most tricky part is to associate language version of field to a users from specific region.
For us, binding it on user groups could work, so user who belongs to group "english-speakers" will automatically see the English version of this fields and fill them in English (and our IT team could start interact with reporter on English without trying to guess is it comfortable for him to answer on English). And if user belongs to another group, like "russian-speakes", the story will be the same - Customer Portal will suddenly become Russian-versioned and there will be no any misunderstanding for users who read in English only with google translate.
For related Confluence space we can make a translated KB articles in separate parts of this space, so we'll not lose this functionality for multilingual Customer Portal.

I am interested in learning more about how you see this working.

We are currently producing "static" language packs for JIRA Service Desk and will ship in the future with German, French, Spanish and possibly Japanese. translations.atlassian.com will be able to be used by customers to produce other languages.

However about I think you are talking about I18n of the dynamic data of JIRA ServiceDesk.

For example you have the Summray field in JIRA that you want to call "What problem do you have?" which in Spanish you may have as "¿Qué problema tiene usted".

The administrators of SD would have to be happy to pump in multiple language versions of these strings. Are you saying this is not a huge problem for you in terms of time and effort? How many different languages do you think you would need? 1, 2, 5, more?

The user experience (UX) around entering these alternate strings would be quite heavy. While I have some ideas about what might work I am interested in how you see such an interaction.

Brad Baker
JIRA ServiceDesk architect

As multilingual corporation we definitely need this feature in JSD.