Creating a new project creates new schemes and workflow. How to stop this?

I create a new project called "My Project" with key "MY".  When I do that, the following also get created

  • MY: My Project Issue Type Scheme
  • MY: My Project Issue Workflow Scheme

Most projects will use already existing schemes.  In fact, it's extreme rarely that a project needs something new.  So this automatic creation of an Issue Type scheme and a Workflow scheme just adds cleanup tasks that have to be done every time a new project is created.

A new project is automatically assigned the already-existing Default Permission Scheme.

It's automatically assigned the already-existing Default Notifications scheme.

And the already-existing Default Issue Type Screen scheme.

And the Default Field Configuration.

So why does it have to get a new Issue Type and Workflow schemes.  Why can't it just be assigned the defaults for those?

2 answers

1 accepted

5 votes
Accepted answer

Use the JIRA default template to create the projects.  The templates determine whether new schemes are used or existing ones chosen, and the last option on the list is set up to simply take the standard lot.


Where do I choose JIRA default template when creating new projects?

After clicking the Add Project button the Select Project Type dialog appears and presents six types. If you chose the last one, Jira Classic, when the project is created it uses the already-existing default schemes. If, on the other hand, you select on of the other types, new schemes are created. The new schemes are based on the defaults, are essentially copies of them. But they are new, separate schemes. In my case, what was bothersome was I was creating several new projects that were all supposed to use the same schemes. But I was getting a new, separate scheme for each one. Half a dozen identical schemes where I only needed one. So now I select Jira Classic almost every time I create a new project.

Pretty much what I do too - unless I've got a good reason to choose one of the others, I stick to Classic. The others are useful, but most of the time, I'm going to need to tweak whatever I choose

Thanks a lot, I think Classic is a bit confusing, since it is the same name as the old classic boards not used any more.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,111 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you