How to delete duplicated Issue Types and Resolutions that are created with system default language

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

To remove duplicated Issue Types and Resolutions in multiple languages.

Issue Types and Resolutions are created depending on Default language settings so that creating new project after changing default language makes duplicated Issue Types and Resolutions in the new language.

JRASERVER-43539 - Getting issue details... STATUS

Solution

In this section, I will explain how to change Japanese Issue Types and Resolutions to English as an example.

  1. Change default language in Jira admin > System > General configuration > Default language Japanese to English

  2. Create new project

    1. Issue Types and Resolutions are created automatically in English

For Issue Types

  1. Connect new issue types with current projects. See more details in Associating issue types with projects

    1. Click Project settings > Issue Types > Actions > Edit issue types

    2. Drag and drop an English issue type from the Available Issue Types list on the right to the Issue Types for Current Scheme list on the left

    3. Follow the migration wizard and change existing Issue Type to new Issue Type


  2. Delete Japanese Issue Types from Jira admin > Issues > Issue types

For Resolutions

  1. Delete Japanese Resolutions from Jira admin > Issues > Resolutions

  2. Select new resolution in wizard screen


You need to update all filters associated with deleted issue types.

JRASERVER-30467 - Getting issue details... STATUS



Last modified on Feb 8, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.