-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Highest
-
Affects Version/s: 8.5.9, 8.8.1, 8.14.1, 8.15.0, 8.16.0
-
Component/s: Custom fields, Data Center - Archiving, Navigation - Search
-
None
-
8.05
-
42
-
Severity 3 - Minor
-
472
Summary
While navigating to the Search for issues page, the Jira log files are filled with FieldLayoutItem errors regarding null values:
Steps to Reproduce
- Deploy a Jira Software 8.5+ instance
- Navigate to Issues > Search for issues
Expected Results
No error is thrown in the logs
Actual Results
Below exception is thrown in the atlassian.log file:
2021-03-03 15:47:40,067-0300 http-nio-48141-exec-14 ERROR USER 947x680x1 1mngg04 0:0:0:0:0:0:0:1 /issues/ [c.a.j.issue.fields.DefaultFieldManager] FieldLayoutItem for field named Archived with ID archiveddate is null. Usually this is a transient race condition due to concurrent modification. Please contact Atlassian support if you see this log message frequently. 2021-03-03 15:47:40,067-0300 http-nio-48141-exec-14 ERROR USER 947x680x1 1mngg04 0:0:0:0:0:0:0:1 /issues/ [c.a.j.issue.fields.DefaultFieldManager] FieldLayoutItem for field named Archiver with ID archivedby is null. Usually this is a transient race condition due to concurrent modification. Please contact Atlassian support if you see this log message frequently.
Workaround
If the custom field is linked to a specific plugin, you may try to disable and re-enable the plugin to verify if the issue stops, otherwise a cold-restart (stopping all the nodes) of the instance was reported as solving the problem on some scenarios.