Issue Summary

Moving an Epic to a Parking lot in the Solution layer's backlog also moves the Epic to the Parking lot in the Portfolio layer.

This is reproducible on the Data Center: Yes

Steps to Reproduce

1. Login with the "Program Manager" role. (Refer to the screenshots attached for Role permissions).
2. Navigate to Portfolio -> Choose the name -> Backlog
3. In another browser tab, navigate to Solution -> Choose the name -> Backlog
4. Change the dropdown from Capability backlog to "Portfolio epic backlog" in the solution layer.
5. Find an epic that is in common with both tabs.
6. Now change the rank of an epic in the Solution layer.
7. Refresh the Portfolio layer, you will see the rank in Portfolio is unaffected.
8. Now move the epic to the Parking lot in the Solution layer. We observe that it is moved to the Parking lot in the Portfolio layer as well.
9. Look at the audit logs for the Epic and it specifies that Rank is modified in the Solution layer. However, for the Parking lot it doesn't show the layer details.

Expected Results

1. Block the permissions for the user to alter the backlog for Portfolio epics of the Portfolio layer from the Solution layer's backlog.
2. Customer expects that when a user is at the Solution layer, they shouldn't be having any permissions to move the backlog of the Portfolio layer (as we already see the rank/features aren't affected).

Actual Results

1. Moving a Feature to a Parking lot from the Solution layer isn't moving the feature to the parking lot in a Portfolio layer.
2. Changing the Rank of the Epics from the Solution layer isn't changing the rank of the epics in the Portfolio layer.
3. However, moving the epics to the Parking lot from the Solution layer is moving the epics to the Parking lot in a Portfolio layer.

Workaround

Currently, there is no known workaround for this behaviour.