Space exporter does not groom notifications properly

Summary

The Confluence Cloud space exporter is leaving notification data in space exports which cause problems in Confluence Server once those spaces are imported.

This prevents Confluence server from being able to manipulate content in certain ways after the space is imported. So far, we have seen this prevent admins from deleting the space, as well as preventing admins from enabling Collaborative Editing in Server.

While there are workaround for Confluence Server, we should fix the root of the issue in Cloud to prevent the problem from occurring. The data in the space export should not contain the notifications which induce this behavior.

Environment

Confluence Cloud > Space Exported > Imported to Confluence Server

How to Replicate

1. Export a space from Confluence Cloud
2. Import it to Confluence Server
3. Attempt to either:
   • Enable Collaborative Editing: CONFSERVER-55576
   • Delete the imported space: CONFSERVER-52755

Symoptoms

Either of the following in the atlassian-confluence.log files on Server:

Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table "content" violates foreign key constraint "fk_notifications_content" on table "notifications"
  Detail: Key (contentid)=(4423910) is still referenced from table "notifications".

could not execute statement; SQL [n/a]; constraint [fk_notifications_content]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement
org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint [fk_notifications_content]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement at 

Workarounds

Workarounds for the Server end are detailed in their respective tickets:

• Enable Collaborative Editing: CONFSERVER-55576
• Delete the imported space: CONFSERVER-52755