Issue Summary

This is reproducible on Data Center: (no)

Steps to Reproduce

1. Create two projects with two different permission schemas, one that the user has edit issue permission but another one doesn’t,
2. Then create one story issue in the project that the user has an edit issue permission
3. After that create a epic in another project that the user has no edit issue permission
4. FInally go back to the story issue and try to assign that epic as a parent to it

Expected Results

An error message is shown, and the parent is not updated.

Actual Results

Now the user can update the Parent field and once the ticket is refreshed the Parent value field is missing.

Workaround

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