Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-34751

Importing an XML Export does not create inline tasks and comments correctly

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Fix description

      Hello everyone,

      The fix for this issue will not fix the links for XML exports that are already imported, but will prevent the issue from happening on newer import jobs.
      This applies to Space XML exports prior to Confluence 7.0.1 as well, and they will not hit into this issue if imported into Confluence 7.0.1 and later.

      Steps to Reproduce
      1. Create a new Space
      2. Export the Space as XML
      3. Delete the Space you just created
      4. Import the Space Export
      5. On a page, create the Task Report Macro, and point it at the imported space.
      Expected Result

      The Task Report Macro should show the tasks that are incomplete, or complete (depending on the settings). Using this example, the report should show 4 incomplete tasks (from the default home page)

      Actual Result

      The Task Report Macro doesn't show the tasks that are incomplete. Marking a task as complete and then incomplete doesn't show the task either.

      The task does not appear in the database.

      Workaround (not applicable to Confluence Cloud)
      1. Perform a full backup of the Confluence Database
      2. Shutdown Confluence
      3. Execute the following SQL Queries:
        delete from "AO_BAF3AA_AOINLINE_TASK";
        delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build';
        
      4. Start Confluence

      Confluence will re-migrate any inline tasks to the new inline task format, which will correctly re-add the tasks not handled when importing.

      Notes

      It is possible to tweak the migration task thread number to speed up the process. To do so, add the following system property to the instance before starting the process:

      CATALINA_OPTS="-Dtasklist.storagetoaoupgradetask.numthreads=18 ${CATALINA_OPTS}"
      

      To define the ideal number of threads for the process, we can use the following formula:

      ideal_thread_number = availableProcessors() * 2 + 2;
      

      Attachments

        Issue Links

          Activity

            People

              lgrzyb lukasz
              dnorton@atlassian.com Dave Norton
              Votes:
              32 Vote for this issue
              Watchers:
              46 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: