Could not read: null for class Artifact for class Artifact
Article ID: 74827
CA OPS/MVS Event Management & AutomationCA Agile Central On Premise (Rally)CA Agile Central SaaS (Rally)
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?
Release: Component: ACPREM
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.