Need way to recognize translated issue types and resolutions

Problem Definition

This feature request stems from JRACLOUD-43539.

Because of the current product design of JIRA, the same issue types or resolutions could be created as different things depending on the system language when creating new project.

For example, issue type "Bug" and "バグ" (it means "Bug" in Japanese) are created in the following scenario.

1. Set the system language to English
2. Create a Scrum software development project
3. Issue type "Bug" is created if it doesn't exist
4. Change the system language to Japanese
5. Create another Scrum software development project
6. Issue type "バグ" is created even though "Bug" exists

After that, both of the issue types are shown as "バグ" due to the translation feature in case user language or system language is set to Japanese. (FYI. "バグ" is the default translation for "Bug".)

Please see the following screenshots which were taken when I associated issue types to screen scheme.

• English
  
• Japanese
  

Then, users cannot recognize which issue type they should use unless they change their language setting back to English.

It might be an expected behavior but it would be stressful for non English customers who didn't know the product design. At worst, they don't even notice what's going on in the screen which they're look at.

Suggested Solution

In my opinion, there are several type of solutions. The followings are just for the examples. Any better solution is welcome!

1. Provide a way to recognize translated issue types and original issue types
2. Alert users when new issue type is created in case that the issue type name has already been taken for translation of other issue type