The user sees a generic entity error which does not give a clue about the real origin of the problem. This is the error:
The null custom field may be caused by two reasons:
- Its custom field type is defined in a plugin that was disabled (more likely)
- The custom field was deleted and some custom field values were left behind (quite unlikely)
The fix covers both cases. In the first one, it will issue a useful message as defined in PCP-384 Resolved . the second one will be ignored, as there is nothing the user can do in that case (maybe except removing the orphaned custom field value).