Jira server throws non-orderable field errors for field layouts after upgrade
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
After upgrading JIRA, the following appears in <jira-home>/logs/atlassian-jira.log:
1
2
3
4
5
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22203'.
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22204'.
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22203'.Cause
A custom field was removed (or if a custom field is from a disabled plugin), but the reference to it in the
FILEDLAYOUTITEMtable was not removed.
Resolution
This can usually be fixed by running the Database Integrity Checker with the 'Check Field Layout Scheme Integrity' and 'Check field layout schemes for references to deleted custom fields' options selected.
There are other possible causes that could make the error to occur which are not fixed by the Integrity Checker. If that's the case and the problem continues to happen on your environment, please reach to Support so that we can evaluate your scenario.
Was this helpful?