I create a new project called "My Project" with key "MY". When I do that, the following also get created
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?
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.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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!
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