Could not read: null for class Artifact for class Artifact

Document ID : KB000074827
Last Modified Date : 26/03/2018
Show Technical Document Details
Question:
What could be causing the error; "Could not read: null for class Artifact for class Artifact" on the Iteration Status page after the Workspace Admin added several Custom Fields?
Answer:
This was caused by a name conflict of Custom field being named 'Requirement' which is already in use in the application.  Note that this was reported in an older version of Agile Central On-Premise which allowed creation of the field with a conflicting name.  Renaming the custom field eliminated the error.