Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira creates new translated issue types depending on the admin profile


Today I became aware of an unfortunate behavior of Jira 7. When creating new projects Jira offers now predefined project types like Scrum/Kanban/Basic software development. 

Each project template contain a predefined set of issue types and workflows, which is useful for simple projects.

The workflows are using the same status names (like Backlog, Selected for Development, Done) independent of the language profile of the Jira administrator.

However for the issue types a language specific set of issue types is created, depending of the profile language of the admin. If you have an international set of admins, you will end soon with a set of duplicate issue types for different languages. This becomes weird if you already added translations to the standard set of issues types. For example in this case a German user could see the original issue type "Task" with the German translation "Aufgabe" and a new issue type also named "Aufgabe" if a German admin has created the project. This leads to max confusion. 

What do you think, is this a useful behavior?


MichaelCreate Project English.pngCreate Project French.pngCreate Project German.png


We've been encountering the problem recently too. Sadly we figured it out after the project has been created. So we had to cleanup all the newly created issue types.

Is there any Jira version where this has been fixed?

It seems to be fixed in Jira 8.5.

Same problem for me but in Portuguese, even choosing all English in the install continuous to create Issue Types in portuguese... 

same problem here. Any updates on how to fix this?

We also have same issue in Japanese. 

As a workaround, I changed admin account language and browser language, then create issue types. 

For fresh install, OS default language (and/or language for service running user) should be changed to English. 

It seems that this behaviour has changed recently. At least during my tests with Jira 8.5 and Jira Service Desk I found that Jira creates issues types based on the default language that is set in the general configuration of Jira. This is much better than it used to be.


Log in or Sign up to comment