Details
Description
This issue occurs when multiple instances of issueFunction custom field have been accidentally added to the instance and is triggered because of a backwards incompatible change in Jira 8.10 tracked as JRASERVER-71423.
Workaround:
Please see this KB article.