java.lang.IncompatibleClassChangeError while editing issues or filters or adding custom field

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

Symptoms

The user is not able to edit or delete issues or filters. In general the error occurs on any action related to custom field.

The following appears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 9 java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ... Caused by: java.lang.IncompatibleClassChangeError: Found interface com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptor, but class was expected at de.phil.jira.plugin.OverdueField.getHoursToAddToDuedateParam(OverdueField.java:38) at de.phil.jira.plugin.OverdueField.getValueFromIssue(OverdueField.java:63)

Cause

The error is caused by a third-party plugin installed on the instance that is not compatible with the JIRA version. In order to find out the name of the plugin, look closely on the 'Caused by' section of the stack trace. In this case, it is the 'Overdue' plugin.

Resolution

  1. Disable the incompatible plugin through the UPM, as in our Managing JIRA's Plugins documentation so the JIRA instance will be usable.

  2. Identify the plugin developer on the Atlassian Marketplace and contact them directly with the error.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.