Automation for Jira rules fail with the exception "No serializer found for class"
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
Automation for Jira rules fail, and in the atlassian-jira.log we see an error message like this:
1
2
3
4
2021-09-13 20:25:07,477-0400 automation-event-serializer:thread-1 ERROR myuser 820x1204x1 ukuha7 192.168.1.11 /secure/WorkflowUIDispatcher.jspa [c.c.jira.transform.IssueBeanTransformer] Error transforming issue with key 'PROJ-100' to automation issuebean.
org.codehaus.jackson.map.JsonMappingException: No serializer found for class com.atlassian.jira.issue.history.ChangeItemBean and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationConfig.Feature.FAIL_ON_EMPTY_BEANS) ) (through reference chain: com.atlassian.jira.rest.v2.issue.IssueBean["fields"]->java.util.HashMap["customfield_12409"]->java.util.ArrayList[0])
at org.codehaus.jackson.map.ser.impl.UnknownSerializer.failForEmpty(UnknownSerializer.java:52)
at org.codehaus.jackson.map.ser.impl.UnknownSerializer.serialize(UnknownSerializer.java:25)Diagnosis
NA
Cause
There are two most likely causes:
The referred class belongs to a custom plugin, and it doesn't have a serializer. In this example, it's a native class in Jira:
com.atlassian.jira.issue.history.ChangeItemBeanThe custom field in the reference chain is a scripted custom field and it's failing. In this case, it's the
customfield_12409
Solution
The solutions are, respectively:
Engage the plugin vendor;
Fix the scripting in the custom field. To get more information about this custom field, use the REST API or check the
customfieldtable in the database.
If that doesn't fix the issue, please engage Atlassian Support.
Was this helpful?