Atlassian Note - Aug 24th, 2023

Howdy, howdy!

We have developed a fix for this bug, which is why we are setting it up as a closed one.

As not all the customers were affected by this bug, we are rolling out the fix gradually to all sites, but if you are being affected by this issue, you can reach out to us by raising a support ticket on support.atlassian.com and our team will enable the fix in your site!

Cheers!

Issue Summary

When performing a space export, we expect to only export the contents of a single space.

In certain situations where the database is corrupted in subtle ways, we will sometimes get multiple spaces exported.

The symptom is that the entities.xml file contained in the export will contain more than one space. Searching for object class="Space" will return more than one result.

Steps to Reproduce

1. Export a space
2. Import to confluence server

Expected Results

Only 1 space get imported to Confluence server

Actual Results

2 space get imported to confluence server

Workaround

As for the workaround on this one, on past cases, it was possible to import the space export without any issues after modifying and editing the entities.xml file of the space export that you are trying to import.

If you open the archive and look at the .xml, there is a part where it references two spaces, you can see by searching with:

object class="Space" 

The workaround consists in deleting the object class = "Space" that is referencing to the space, and all the content within the object (basically starts on the object class= "space" and delete everything, including the </object>), on the entities.xml, for the space export not related to the target spacekey.

That being said, you can try to modify it and then trying to re-import the space again.