How to edit default issue type scheme

[Coiram]

This question has been asked already on 17 October 2011 and to date it is still present as HUGE bug on Jira - 8.0.2  see thead:

https://community.atlassian.com/t5/Jira-questions/How-to-edit-default-issue-type-scheme-or-how-to-remove-issue/qaq-p/347379  

Jira developers should know that it becomes very hugly and unpleasent the administration of "scheme associatons" when the system has several hundreds projects.

It is time Jira gets the definition of MASTER ISSUE SCHEMA not copy of a copy of a copy

When Atlassian will get this implemented?

.

[Andy Heinzer]

Hi Mario,

I can feel your frustration here in regards to not being able to customize this default issue scheme type.   But given that JRASERVER-11222 was closed as obsolete, and from that description, Dave Meyer posted this update:

As of JIRA 7 (released on October 6, 2015), new projects are not created using the default issue type scheme. Depending on which project template you choose, a fresh set of schemes will be created for you. These new schemes do not use the default issue type scheme.

If you would like to create a project that uses the same schemes as an existing project, we have introduced a new "Created with shared configuration" feature when creating projects. Simply select an existing project, and JIRA will create a new project that shares all the same schemes as the existing project. Learn more here.

This default issue type scheme actually isn't used when creating projects in Jira anymore.  I believe it's actually a hold-over from much older versions of Jira 6.x and considerably earlier versions.  I did come across the feature request of JRASERVER-8926 which seeks to be able to customize this default issue type scheme, however I fear that it too will get the same kind of response as the other ticket, because current versions of Jira are using either project configuration templates (which create new schemes) or shared configuration templates when creating new projects.

So I'm interested to understand how you're using this default issue scheme, since it appears to be largely unused by current project creation methods.  You can still associate this with current projects, but I'm not sure why you would want to here.  Since you can't actually add additional issue types to this system default, it can defeat the purpose of being able to make changes to any projects that use this issue scheme.

I'm interested to learn more about the use case here, and understand the pain-points here.

Regards,

Andy