Could not load custom field type plugin with key 'XX'
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Symptoms
A custom field may be missing from all screens and the custom fields page in JIRA, and cause ERROR log entries on JIRA startup.
The following appears in the atlassian-jira.log:
2012-10-12 10:35:41,472 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'XX'. Is the plugin present and enabled?XX will be replaced by the name of the class that defined the missing issue type.
Cause
A custom field was in use which was defined by a plugin, and that field type has been removed. This could be because of:
- The plugin was uninstalled
- JIRA was upgraded to a version for which the plugin is no longer compatible
- The plugin redefined or removed that custom field
Workaround
- Go to the Custom Fields page in Administration
- If no custom fields exist, create a dummy field
- Copy the link of the "delete" link
- Paste that into the URL bar, modify the id to match the missing custom field, then hit enter
- Remove the dummy field, if created
Resolution
If the plugin was uninstalled
- Reinstall the plugin
- If the custom field is not required anymore, then remove it and uninstall the plugin
If JIRA was upgraded to a version where the plugin is no longer compatible, and a newer compatible version of the plugin exists
- Upgrade the plugin
If JIRA was upgraded to a version where the plugin is no longer compatible, and no newer compatible version of the plugin exists
- This only will work if you have not yet changed anything in JIRA since upgrading
- Revert to the state of JIRA before the upgrade
- Remove the custom field
- Uninstall the plugin
Re-perform the upgrade
If any of these resolutions has been applied and you are still seeing the errors
- Please reach out to Atlassian Support at https://support.atlassian.com.
- Please attach a Support ZIP with the Support Request for any further investigation.