Issue Summary

When updating a Capability with an API PATCH to it's customfields, other fields can end up being modified as well, despite not being included in the PATCH call

Steps to Reproduce

• Enable a customfield for Capabilities in Details Panels Settings for your Portfolio
• PATCH the customfield through API
  e.g

  [
    {
       "op":"replace",
       "path":"customfields/0",
       "value": {
         "customfield_90387": [ {
           "value":"Reasons"
           }
          ]
        }
     }
  ]

• Check the Audit Log for the Capability and see a different field has been modified as well.
  e.g.

  By Jose Sanchez via API on 1/15/2025 12:30:16 PM
  Capability Updated -
  Blocked_Reason Changed - From [Because] To [Reasons]

  By Jose Sanchez via API on 1/15/2025 12:30:16 PM
  Capability Updated -
  GlobalRank Changed - From [2055] To []

Expected Results

The PATCH will update only the field(s) included in the body of the call.

Actual Results

Seemingly random fields are updated. This also does not occur consistently.
Further investigation finds that these updates are showing old changes made on the backend that were not logged to the audit log.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available