Translate field values

Question

Hello,

we have customers who speak various languages, so we'd like to translate the _values_ of (system and default) fields into different languages.

So this would be the ideal logic: If a field has only one translation, display this (obviously). Else, if the field has multiple translations, display the one that matches the user's account preferences.  Else, display the default translation.

Is something like this possible?

Thanks,
Ingmar

Christopher Maxwell · Answer

@Ingmar Heinrich That makes sense.

Unfortunately, what you are looking for is not available within Jira by default.

Jira ships with a number of built in translations, but this is for the field titles, not contents. The way the logic works is that a Jira administrator can choose the default language for the site, however, individual Jira users can also choose their preferred language which overrides what the Jira admin has selected (more info: https://confluence.atlassian.com/adminjiraserver/translating-jira-938847004.html). Yet again, this is for titles.

Translation of field contents is available a few ways. As I'm sure you are aware, most browsers have some type of translation feature built in. For example, Chrome (https://support.google.com/chrome/answer/173424?hl=en&co=GENIE.Platform%3DDesktop), and Firefox (https://www.mozilla.org/en-US/firefox/features/translate/).

I recommend, though, that you check out the Issue Translation for Jira app in Jira Marketplace (https://marketplace.atlassian.com/apps/1226752/issue-translation-for-jira-translate-to-any-language?tab=overview&hosting=cloud). The app utilizes Google Translate to enable site users to translate the contents of fields. While not an ideal solution, this may be workable for you.

Ingmar Heinrich_t6cdfy · Answer

@Christopher Maxwell the contents. Thing is that we, as an agency, have customers with various language requirements, so we need to be able to provide field content in multiple languages.

Christopher Maxwell · Answer

Hi Ingmar,

Are you referring to translating the titles of system and default fields, or the values within the fields themselves?

For example, the term "Summary" itself, or the contents of the ticket's summary?