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?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs