Deleting schemes, etc with defaults in place / deleted projects

[Jared G]

I struggled to give this an accurate title, so I'll describe the best I can.  I am struggling to delete just about anything (typically schemes are my sticky point) from my Jira instance due to various ties, that I cannot untie.  Typically, it's because the project was deleted, or a default exists so it will not allow me to. 

Said another way, the default issue type, as listed under any scheme cannot be untied, thus I cannot delete the scheme. Screen shot may explain this more accurately.

Thanks in advance for any help!

[Joseph Chung Yin · Accepted solution]

@Jared G -

Hi Jared:

It regards to configuration scheme for projects, you cannot remove "Default" because it is part of the application.  Deleting a project doesn't remove the schemes associated with the project.

Example, for issue screens configuration, you will need to delete the screen first, then delete the screen scheme, and finish up with deleting the Issue Type Screen scheme.

Example -

  

Hope this makes sense.  What object scheme that you are trying to remove from the system?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Jared G]

Thank You Joseph!  It makes sense, and I do understand that a default must exist, as any given unmapped operation must have some sort of default.  I'm not too hung up on the various parts not deleting with the project, just how to delete them now.

It sounds like what you may be suggesting is to start with the smallest piece and work up? So delete any relevant screens, then the screen scheme, then the Issue Type Screen Scheme?

I'm not sure I understand your final question, I'm sorry!  So taking it back to the initial question, in my screen shot, if I want to delete the "NAV: Jira Service ..... " Issue type screen scheme, I would have to somehow delete the screen scheme first?

Thanks again for the help and breakdown.  I'm about 3 years into learning JIRA and this type of thing still eludes me.  I appreciate your time.

[Joseph Chung Yin]

@Jared G -

Thanks for your update.  So your understanding is correct.  One cannot delete the grand parent scheme unless you start from the bottom (kids > parent > grand parent)

In this case - Issue Type Screen Scheme (grandparent) >> Screen Screen Scheme (parent) >> Screen(s) (kids).

Hope this helps.  If it resolved your ask, then please click on Accept answer to my posting so others with similar asks will see this posting as an answered one.

Best, Joseph

[Jared G]

Hi Joseph,

Thank you again.

I meticulously went through all screens and verified that all screens potentially tied to the scheme in question were deleted.  From the screen settings, I can see all the ties to screen schemes, and workflows, and no screens exist that would sit in the scheme I need to delete.  If there is another menu system that may display screens in another way, perhaps some are hidden somehow?  I found the link https://sitename.atlassian.net/secure/admin/listworkflows.jspa which was new to me and presents the workflows in a much easier to read format.  Is there a link like this for screens?

I've included a screen shot to ensure I'm illustrating my question properly.  In the screen shot with the red #1, these are the issue type screen schemes I need to delete ie: "NAV, NCO3, NCO, and SALE.  As you can see they're currently connected to the "IT support screen scheme" - which I can switch, this is where they are landing for now.

Once I click on the issue type screen scheme (from the page previously mentioned), it opens the page shown in screenshot #2.

So I can tie Issue Type screen schemes to other screen schemes, but they must be connected to something a screen scheme so all I can do is move it around.

Apologies if I'm WAY off base.  I realize I'm missing the mark but I'm clicking all around and things just aren't coming together as they should.

[Joseph Chung Yin]

@Jared G -

Thanks for your update.  Based on your latest image screen shot, there is a possible problem now as the IT Support Screen Scheme is shared by multiple other projects' Issue Type Screen Schemes.

I hope you have not made any changes yet against IT Support Screen Scheme because the scheme is shared with other projects. 

When making changes to scheme objects, you need always make sure the scheme it is not shared with other projects first.  It is because any changes will impact all other projects.

To check for scheme usage (now let's just focus on Screen Scheme), one should access "Settings" >> Issues >> Screen Schemes to identify which Issue Type Scheme(s) use it.

At this time, what you need to check on other Issue Types Screens Scheme to remove the usage of IT Support Screen Scheme in them + ensure the changes that you made to the IT Support Screen Scheme didn't impact those other projects.  If not, then you can just update those Issue Types Screens Schemes to remove the call out to IT Support Screen Scheme first, then you will be able to properly remove the IT Support Screens Scheme from the system assuming you already deleted/unassociated the "Default" screen.  

Afterward, you can then remove NAV: Jira Service Management Issue Type Screen Scheme.

Lastly, don't forget to check the screen object associated with the IT Support Screen Scheme is not used by other projects too.  You can find it out by accessing "Settings" >> Issues >> Screen

Hope this helps.

Best, Joseph

[Jared G]

Thanks Joseph.  Below is some feedback on your wonderful reply:

Based on your latest image screen shot, there is a possible problem now as the IT Support Screen Scheme is shared by multiple other projects' Issue Type Screen Schemes.

Luckily, our environment is very young and mostly unused so I have some freedom to play around without great impact.  I had switched to the IT Support Scheme just for this issue I'm dealing with, but I went ahead and switched it to another.

At this time, what you need to check on other Issue Types Screens Scheme to remove the usage of IT Support Screen Scheme in them + ensure the changes that you made to the IT Support Screen Scheme didn't impact those other projects. 

I reviewed all the Issue Type Screen Schemes, and the IT support Issue Type Screen Scheme is not in use anywhere else. Therein lies my problem, I can only change it to something already in use.  Is there a way to disconnect it without choosing another scheme that is already in use?  Should I create a "dummy" screen schemes to move it to?

If not, then you can just update those Issue Types Screens Schemes to remove the call out to IT Support Screen Scheme first, then you will be able to properly remove the IT Support Screens Scheme from the system assuming you already deleted/unassociated the "Default" screen.  

May be the same answer as before but I did view the Issue Type Screen Schemes in full, and there is no call out now to the IT Support Screen Scheme.  I get what you're saying though - there's no call out to it because I changed it, but again, I can only change it to something already in use. 

[Jared G]

I don't think this uploaded with my reply

[John Funk · Accepted solution]

Hi Jared,

You might want to take a look at the Revyz Configuration Manager for Jira app in the Marketplace. You can do a free trial. It will let you do bulk deletes for the items you are wanting to clean up. Full transparency- I am an advisor for the app. 

https://marketplace.atlassian.com/apps/1231935/revyz-configuration-manager-for-jira?hosting=cloud&tab=overview

[Jared G]

Thanks John! I have bookmarked this for further review, it looks promising.  I'm going to continue to try to understand the other answers but this seems to be something that would be helpful.  Thanks again.

[John Funk]

I think it is the only way you are going to be able to delete in bulk, though the other answers work just great for deleting one at a time. 

[Jared G · Accepted solution]

For the sake of the internet, and anyone seeking an answer to this - I ended up getting in touch with Jira support, and it was an easy fix.  They advised to simply fully delete the projects that the schemes had been tied to.  They alternatively suggested restoring the project but either method works.

Once those projects were fully deleted, it was easy to delete the schemes.  Hope this helps someone in the future.

Thanks to those that provided input.