When trying to create an issue as a child of an issue in another project from a plan while grouped by component will appear to fail

Issue Summary

When trying to create an issue as a child of an issue in another project from a plan while grouped by component will appear to fail with a message stating 'Changes couldn't be saved' when trying to write the changes from the Review Changes interface.

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Create plan that has at least 2 projects.
2. Create a component with the same name in both projects.
3. Modify the view settings on the plan to group by component and add the component with the same name from Project A and Project B to the group by clause.
4. Under an issue in Project A (that has the component set) add a child issue in Project B.
5. Also add an issue under that same ticket for Project A as the child.
6. Attempt to write the changes via Review Changes button.

_Notice the Project A issue is written as expected, but the issue for Project B (opposite of the parent issue) it will appear to fail.

Expected Results

Both tickets should be written to the respective projects with the proper components for that project without an error message.

Actual Results

The issue does typically get written (although there have also been instances where the issue is not written properly) and the "Changes couldn't be saved" toaster pop up appears.

Workaround

Currently the only workaround would be to not use the group by View Settings option leveraging the Components.