nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Translation of issue types doesn't have effects

Gisela Lassahn

Hi all together,

we have German as the default language in Jira DC 9.4.8.

As we have more and more users who don't speak German, we decided to store English translations (UK and US) for our issue types and statuses.

But in many important places (not to say almost all important places) the types and statuses still appear in German even for those users who use the other languages.

Is this a known bug or lack? If not: Are we doing something wrong? If yes: Does anybody know if Atlassian plans to remedy it and when?

Many thanks and best regards,
Gisela

Comments

Jeany

Hi Gisela,

this sounds similar to this issue https://jira.atlassian.com/browse/JRASERVER-43381?filter=98912 which is an annoying behavior for us too.

Please vote & watch!

Kind regards,

Janine

Thales Santos

Hi Gisela,

I did a quick test and couldn't find a place where Issue types are not translated, please have a look at JRASERVER-65224 to see if it's something relatable. I also found more references, more specifically to statuses, also did some tests and it looks like it works for the statuses but the transition names were not translated, on that note I have some other references for you with a (not so simple) workaround, check these issues and links:

I would also encourage you to raise a support ticket giving more details of your issue, it would be good to understand what were the changes you made that are not reflecting in the UI and other things.

Hope this helps,

Thales

Gisela Lassahn

Hi Thales,

many thanks!

After restarting Jira, the issue types were displayed with their translations. So it's exactly the phenomenon that is described in JRASERVER-65224.
I've just voted for it and am watching it now.

For JRASERVER-6798 I did it already months ago.

JRASERVER-13728 was closed as an Duplicate of JRASERVER-6798, so I can't vote for it.

And of course we would like to translate our workflow transitions, too.

But the way described in the community is too time-consuming for us as we have lots of different workflows.

Another problem is that in JQL we still have to use the original names of the types and statuses and can't use the translations for them, and that in the workflow view the orginal names are shown instead of the translations.

Best regards,
Gisela

Gisela Lassahn

Hi Janine,

many thanks!

This isn't exactly what I meant, but this is an issue for us, too.

I've voted for it and am watching it now.

Kind regards,
Gisela

Welcome!

It looks like you're new here. Sign in or register to get started.