Problem Definition
Currently, when setting up a project that uses several languages, the translations for the project's assets will be provided like the followings(as of Dec 17th):
| Item | How the translated asset is created |
|---|---|
| Issue type | Depending on the default language used, duplicated items for different languages will be created upon project creation |
| Resolution | same as above |
| Status | translation is provided for the existing items automatically |
| Priority | translation isn't provided automatically |
This is making the project administration very confusing for the admin because several different approaches will be needed to set up a single localized project.
Suggested Solution
Align the behaviour for setting up localized items
Note
- If the admin did the followings, different issue types having the same name would appear.
- Set the browser language setting to Japanese
- Create a project with default language set as English
- Create another project with default language set as Japanese
- Add translations for the issue types created in 2
- Access https://<instance>.atlassian.net/secure/ShowConstantsHelp.jspa
- For issue type, Epic is not created for each languages so it doesn't get duplicated.