Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Deleting Global Issue Type Scheme

Simon Parker March 19, 2021

Dear all,

New to JIRA Service Management administration, and playing around to see if it can be setup for a use case we have. I have used JIRA Helpdesk in the past but only as a user rather than as an admin.

I've tried creating new issue type scheme and have been able to do so without issue. However I am unable to delete one of issue type schemes I created. I've worked out that you have remove a scheme from all projects before it can be removed. This particular scheme though is showing under Projects as 'Global (all unconfigured projects)' for some reason and it will not allow me to delete it.

I haven't found how to remove this status which I suspect I need to do so before I can delete the issue type scheme. I did try looking at the help files but couldn't find any mention of setting a global issue type scheme so not sure what to do.

Any advice would be most welcome.

Kind regards,

 

Simon

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Champion
March 19, 2021

That is a Default scheme that is locked by the system you cannot and should not remove.

Simon Parker March 19, 2021

Hello Jack,

 

Many thanks for your quick response.

It is an issue type scheme that I have created, I was just playing around with creating schemes that might be useful in the future. Not sure why it is different to others that I have been using.

Could you advise how it has become locked so that I don't do it again please?

 

Kind regards,

 

Simon

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 19, 2021

Indeed, in the code, it's actually there to act as a container for the global list of all available issue types, as well as for "project has not got a scheme selected"

Even if it was not built that way, and locked down, there would be no reason to delete it other than removing one line from the list of schemes to slightly reduce complexity for admins.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 19, 2021

Sorry, crossed comments there.

The global default scheme was not created by you, it is built in.  (Although you could have renamed it from "Default issue type scheme"?)

Simon Parker March 19, 2021

Hmm strange. It has a name and description that I entered.

Is it possible that I've essentially renamed the global default scheme by mistake rather than create a new one?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 19, 2021

Crossed again!  Yes, you could rename the default.  It's the help message that gives it away as the default

Like Jack Brickey likes this
Simon Parker March 19, 2021

Ok great, many thanks for your help.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events