How to delete issue type schemes that are not associated with any projects from the database
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The information in this page relates to Database Manipulation in JIRA. Consequently, Atlassian Support cannot guarantee to provide any support for the steps described on this page as database manipulation are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Users would like to manually delete the issue type schemes from the database instead on the JIRA UI
Solution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Do not delete the Default Issue Type Scheme even though it is not associated to any projects
Run this SQL query to fetch the list of issue type schemes that are NOT associated to projects :
1 2 3select id, configname from fieldconfigscheme where fieldid = 'issuetype' and id not in (select fieldconfigscheme from configurationcontext where customfield = 'issuetype');ℹ️ This will list Issue type schemes that are not associated to a project
To delete issue type scheme run this query :
1delete from fieldconfigscheme where id = XXXXX;To delete multiple entires at a time run this query :
1delete from fieldconfigscheme where id in (XXXXX,XXXXX);ℹ️ Replace XXXXX with the id of the issue type scheme which is not associated to any project from SQL query in Step 1.
Restart JIRA for changes to come into effect.
Was this helpful?