We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      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:

      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:

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                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:

                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:

                        Unassigned Unassigned
                        jwyllys Justin W.
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            jwyllys Justin W.
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: