Updating an issue with an invalid parent using the API doesn't return an error

Issue Summary

As a result of Epic and Parent Link deprecation, we’ve asked all marketplace vendors (and general API users) to provide and consume the parent field in all of their API requests, instead of the previous parent_link and epic_link custom fields.

When using the new parent field we do not return an error if an invalid parent issue is provided.

• When providing an epic_link parent, we respond with a HTTP204, but don’t set the invalid parent.
• When providing a parent_link parent, we respond with a HTTP204, don’t set the invalid parent, and clear the existing valid parent.

  Steps to Reproduce

epic_link

1. Create an issue on the base level
2. Call the issue update endpoint with another base level issue provided in the parent field
3. Observe that a HTTP204 is returned and no epic is set for the issue

parent_link

1. Create an issue on the epic level
2. Assign the issue a "Level 2" parent
3. Call the issue update endpoint with a base level issue provided in the parent field
4. Observe that a HTTP204 is returned, the existing parent is delete and the invalid parent is is not set for the issue

Expected Results

epic_link

• A HTTP-4XX is returned with a meaningful error

parent_link

• A HTTP-4XX is returned with a meaningful error

Actual Results

epic_link

• A HTTP-204 is returned and no epic is set for the issue

parent_link

• A HTTP-204 is returned, no parent is set for the issue and the existing parent is deleted

Workaround

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