Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-43539

Changing Default language and creating a new project creates unwanted Issue Types and Resolutions

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When you change the JIRA instance Default language from the default English to Czech (but tested also for German, for example) and you create a new project afterwards, the are new, and seemingly unwanted, Issue Types and Resolutions generated - duplicating the existing ones. See the attached screenshots for an illustration.

      One can imagine all the drawbacks connected with this. One of the problems is that the newly generated Issue Types lack translations -> so you must (re)translate them to English and so on if needed.

      Tested on JIRA 6.4.4, with just the Agile add-on installed.

      The simplest way of how to work-around this issue (or an undocumented feature?) is NOT to switch from the default English language, which is also the best usage scenario in the most cases...

        1. IssueSearch.jpg
          IssueSearch.jpg
          186 kB
        2. jira_duplicated-issue-types.png
          jira_duplicated-issue-types.png
          70 kB
        3. jira_duplicated-resolutions.png
          jira_duplicated-resolutions.png
          56 kB
        4. jira_lacking-default-translations.png
          jira_lacking-default-translations.png
          16 kB
        5. Resolution.jpg
          Resolution.jpg
          111 kB

            [JRASERVER-43539] Changing Default language and creating a new project creates unwanted Issue Types and Resolutions

            Micah B. made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 455828 ]

            Petr Bodnár added a comment -

            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...

            Petr Bodnár added a comment - 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...
            Tomoko Suzuki made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 455828 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3041984 ] New: JAC Suggestion Workflow 3 [ 3691097 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Component/s New: Project - Actions [ 41595 ]
            Component/s Original: Project - Create Project [ 32990 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2618729 ] New: JAC Suggestion Workflow [ 3041984 ]
            Marko Filipan made changes -
            Link New: This issue is related to JRASERVER-67382 [ JRASERVER-67382 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2590587 ] New: Confluence Workflow - Public Facing v4 [ 2618729 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359558 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2590587 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2127025 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359558 ]

              Unassigned Unassigned
              9ef4329541be Petr Bodnár
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: