Hi,
we have upgraded our JIRA to 6.2.7 version. After upgrade we are getting the following message in the logs.
and the custom fields listed the in the logs are not showing in the custom fields section but are available in the database.
Any idea about this issue.
2014-09-20 11:49:28,586 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
2014-09-20 11:49:28,822 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22203'.
2014-09-20 11:49:28,822 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22204'.
2014-09-20 11:49:28,822 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
2014-09-20 11:49:28,939 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22203'.
2014-09-20 11:49:28,940 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22204'.
2014-09-20 11:49:28,940 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
2014-09-20 11:49:29,057 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22203'.
2014-09-20 11:49:29,057 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22204'.
2014-09-20 11:49:29,057 localhost-startStop-1 INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'.
We had the same issue. I found a solution, referenced here: https://jira.atlassian.com/browse/JRA-4423.
Go to Admin > System > Troubleshooting and support > Integrity checker. Choosing "Check Field Layout Scheme Integrity" and run it gave me 10 errors. "Fix" took care of the situation.
The issue is about a removed custom field where the reference to all haven't been deleted.
Thanks Ivar, I had same issue when upgrading from 5.1.1 to 6.4.12 and the Integrity checker works fine!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had JIRA Service Desk 7.0.10 and this worked for me too. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same error, but it's not related to customfields not being removed from field layout schemes, such as these system-fields:
Integrity checker did not point this out as an error. Still hunting down the cause of this error.
On JIRA 6.4.10
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.