Issue Summary

The PATCH API call for the dependencies endpoint to set one specific custom field to null/blank, is also setting other custom field values to blank unexpectedly.

Using the PATCH API call below for the dependencies endpoint to set the specific custom field to null/blank, but it is also setting other custom field values to blank if there are multiple custom fields enabled for Dependency.

PATCH API : /rest/align/api/2/dependencies/<id>

Steps to Reproduce

1. Take a dependency with at least two custom fields active and assign a value to both the custom fields in the UI > Dependency slide out
2. First use the GET API call for the specific depdency to get the Dependency details. This will show the custom field IDs present in the Depedency and their values (customfield_xxx)
3. Then, using the JA REST PATCH API, with the same payload as below, update only one specific custom field value to null. I used a patch API for dependencies and payload as below

PATCH API : /rest/align/api/2/dependencies/<Dependency id>

Payload :
[
{
"op": "replace",
"path": "/customFields",
"value": [
{
"customfield_<xxx>": null
}
]
}
] 

      4. Check the UI > Dependency slide out.

       5. Notice the PATCH API call for the dependencies endpoint to set one specific custom field to null/blank, is also setting other custom field values to blank.

      6. Also see the Dependency Audit log which shows the other custom field values being changed to blank via API.

Expected Results

Only the desired custom field whose value was updated via API should be changed to blank []. The other custom fields values should not be changed by API.

Actual Results

In addition to the desired custom field whose value was updated via API to blank [], PATCH API is also setting other custom field values to blank unexpectedly.

Workaround

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