So this issue is really still not fixed even in Jira 7+ after all the years (while it possibly existed years before creating this issue)? Is it really that difficult to rethink and change the architecture to simple "1 issue type -> N possible type translations"?

I can see this is not upvoted, but how can it be when you close it right away? I can see someone created a duplicate JRASERVER-67382 - closed as well...

I recently encountered this issue too and I raised a support ticket JSP-249726 and finally I went here.
here are my two cents:
Per currently behavior, they will always some issue types "pairs" which have same meaning in different languages in the system.
For example, Bug(English) and 缺陷(Chinese) means same thing although they are in different language, so I have to provide same translation for the other language Japanese.
If i put them within one same issue type scheme, they will appear same name in Japanese, a Japanese user will be confused.
Actually, we won't use them together within one issue type scheme, right? since they means same thing(issue) on earth.
then here comes two cases:
case1: for the future issue types scheme, I only use one issue type either "Bug" or "缺陷", so that the other one will be abandoned by users. One will be useless.
so Jira Agile creates issue types automatically, but eventually makes one useless. from case1 I think this is not good design.
case2: for the future issue type scheme, use "Bug" for some issue type scheme and apply those scheme to some projects and use "缺陷" for the other issue type scheme and apply to the other projects..
this also bring troubles:
1)Japanese users search issues from JIRA issue search may see two same issue type appeared from drop-down list. They are same translation for "Bug" and "缺陷".
2) For some statistics widgets, if it involves multiple projects using these two issue types, they will be counted separately in report, but they means same item.
from case2 I think this is not good design.
I know in JIRA 7 admins is allowed to created project from shared configuration. I still hope there will be a good resolution for this in future.

Hi Mai, thanks a lot for this feedback, I didn't want to bother with this issue until someone else also comes in with a similar opinion that this really is a bug, no matter how good the intention behind was. I see that Dave above tries to "defend" the product but the explanation is just not making much sense to me.

One example for all: One could also do the renaming of the various issue types and lose the sense in the workflow mapping without even switching the language. In another words, meaning of the various issue types should logically always remain the same (it would be a misuse of the JIRA otherwise), no matter what label is currently displayed to the user (based on his, or global JIRA language preferences)!

Hello dmeyer and ohernandez@atlassian.com,

I was wondering if we can reopen and fix it as a 'bug' instead of 'suggestion'. I read your comments and understood that the behaviour is by design, however, I think there might be a design mistake.

• There exist identical duplicate resolutions in Resolve Issue Screen when non-English language is used (see Resolution.jpg).
• There also exist the duplicate resolutions in Issue Search as well when non-English language is used. Further more, the search results are different, depending on which of the duplicate is chosen here and in Resolve Issue Screen (see IssueSearch.jpg)