Creating new project also creates unneeded, unnecessary, UNWANTED schemes and workflows

see https://support.atlassian.com/servicedesk/customer/jst/problem-report-109015

When creating a new project, a new Issue Type Scheme and a new Workflow Scheme are also created. This should not happen as ALL it does is add unnecessary work for the administrator.

A new project is either going to get an already existing scheme, or it's going to need a new one crafted by the administrator. It's not going to need a new plain default scheme. So creating new plain schemes doesn't provide any benefit.

All it does is add two "delete scheme" cleanup tasks that have to be done every time a new project is created. It's either that or the administrator decides not to delete them and watches as a vast number of identical Issue Type and Workflow schemes are created (a maintenance nightmare).

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?

Up until a week ago, the JIRA Classic project type enabled an administrator to create a project without these extra unneeded schemes being created. But, in it's ongoing effort to make things more difficult for administrators Atlassian decided it was a good idea to remove the JIRA Classic project type (while falsely claiming "This project type was duplicated by the Project Management project type").

Bring back the JIRA CLassic project type or at least provide some project type that doesn't create more work for administrators.