-
Bug
-
Resolution: Fixed
-
Low
-
None
-
8.20.3
-
None
-
8.2
-
1
-
Severity 3 - Minor
-
Issue Summary
The Log Analyzer in Jira is triggering a false positive for the problem "Jira server throws non-orderable field errors for field layouts after upgrade" due to the log events found in the application logs not matching the error in the referenced article
Error referenced in Jira server throws non-orderable field errors for field layouts after upgrade
INFO [fields.layout.field.AbstractFieldLayoutManager] Field layout contains non-orderable field with id 'customfield_22205'
Relevant logs found in application logs
INFO [c.a.c.e.c.a.j.i.f.l.field.AbstractFieldLayoutManager.fieldLayoutCache] Cache com.atlassian.jira.issue.fields.layout.field.AbstractFieldLayoutManager.fieldLayoutCache was flushed
This causes it to appear that there is an issue with non-orderable field errors for field layouts in the instance when in fact there is not,
Steps to Reproduce
- Execute the "Log analyzer" by navigating to : Jira Administration > System > System Support > Troubleshooting and support tools > Log analyzer
Expected Results
Based on the logs found in atlassian-jira.log there should not be an entry indicating "Jira server throws non-orderable field errors for field layouts after upgrade".
Actual Results
Log analyzer identifies the problem "Jira server throws non-orderable field errors for field layouts after upgrade" exists and needs correction.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available