Creating new project always creates a new issue type scheme

Still need help?

The Atlassian Community is here for you.

Ask the community

Details

After upgrading to JIRA 6.2, all new projects are created with a new Issue Type Scheme. Before the upgrade, JIRA used to pick the Default Issue Type Scheme. 

Cause

This is part of the new changes being introduced in JIRA which helps new users get started faster. Having a new issue-type scheme can be confusing for the administrator. This article describes how to use shared configurations in order to prevent new issue-type schemes if they are not needed.

Resolution

  • From JIRA 6.2 to 6.3, If you create a project using the Project Type JIRA Classic or Project Management then it would use the Default Schemes (Issue Type, Workflow and Screen) for your project.

  • After JIRA 6.4, If you create a project using the Project Type JIRA Default Schemes (JIRA Classic was renamed) it would use the Default Schemes (Issue Type, Workflow and Screen). The Project Management type now creates its own Schemes.


  • After JIRA 7, You can create a project using a shared configuration of an existing project. See the screenshot below.

Last modified on Nov 14, 2022

Was this helpful?

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