You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?