Inconsistent rest api behaviour when setting parent issue when epic link is not on update screen

Issue Summary

Trying to use "parent" field instead of "Epic link" to update issue epic with respect to "Deprecation of the Epic Link, Parent Link and other related fields in REST APIs and webhooks" (see https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048)
Sending following request to update issue epic to "Edit issue" (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put)

{
    "fields": {
        "parent": {
            "id": "10014"
        }                    
    }
} 

In all cases it works fine.
However if "Epic link" field is removed on project "Configure Screen" then "Edit issue" responses with HTTP 204 (success) but actual issue's parent change does not take place.
Is this possible to modify "Edit issue" either to response with HTTP 400 to indicate error in this case or to update issue's parent independent whether "Epic link" field is configured for screen or not.

Steps to Reproduce

1. create team managed scrum project
2. add epic issue and note its id
3. add regular issue
4. remove "epic link" from edit screen associated with project/issue type
5. make rest call to update "regular issue" from 3rd step, pass issue id from epic created in step 2
   Unknown macro: { "fields"}
   } 

1. Jira responds with 204 even though the epic link is not available on edit screen

Expected Results

it depends.

• return 400 response - reasoning: for other fields when the field is not available on screen and we want to update it through rest api then 400 response is returned
• or allow updating "parent" field as it's kind of "meta field" - but it seems to be breaking the field on screen security abstraction.

Actual Results

Jira returns 204 but does not update the parent

Workaround

none so far