Removed child pages are not getting deleted but moved to the root level when using Remote publishing

Description:
Child pages of (versioned) pages which are first published to a remote space and then removed in the source space (= remove change), are not removed completely, but instead only moved to the root level. This affects page hierarchies if the root page and child page are removed and then published to a remote space.

Steps to reproduce:

1. Setup VSN in a source space with at least one version, connect target space with Scroll Remote Publishing Endpoint installed.

2. Create a hierarchy in the source space with a root and child page (compare attachment)

3. Publish to remote space in one version.

4. Now delete root and child page in that version.

5. Publish again to remote space.

Expected result:

• Child and root page are removed.

Actual result:

• Root page is removed, but child page is on the top level. (Check this by accessing "Pages" below the space home page and take a look at the available pages, see second screenshot)

Note:

• The issue might be that the root page is removed first and Confluence then moves the child page to the root level automatically, but now the source hierarchy doesn't match the hierarchy in the target space.

• Also test if the result is visible with only removing the root page.

• Using the local publishing mechanism, the problem didn't arise, but should be tested again.