-
Bug
-
Resolution: Fixed
-
Medium
-
5.5.2, 5.8.5, 6.0.5, 6.0.7, 6.6.7
-
40
-
Severity 2 - Major
-
28
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
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
- Create a new Space
- Export the Space as XML
- Delete the Space you just created
- Import the Space Export
- 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)
- Perform a full backup of the Confluence Database
- Shutdown Confluence
- Execute the following SQL Queries:
delete from "AO_BAF3AA_AOINLINE_TASK"; delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build';
- 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;
- is duplicated by
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[CONFSERVER-34751] Importing an XML Export does not create inline tasks and comments correctly
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 75874 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 537388 ] |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-34751]. {panel} {panel:title=Fix description|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff} 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. {panel} h5.Steps to Reproduce # Create a new Space # Export the Space as XML # Delete the Space you just created # Import the Space Export # On a page, create the Task Report Macro, and point it at the imported space. h5.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) h5.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. h5.Workaround (not applicable to Confluence Cloud) # Perform a full backup of the Confluence Database # Shutdown Confluence # Execute the following SQL Queries: {code:sql} delete from "AO_BAF3AA_AOINLINE_TASK"; delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build'; {code} # 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. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-34751]. {panel} {panel:title=Fix description|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff} 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. {panel} h5.Steps to Reproduce # Create a new Space # Export the Space as XML # Delete the Space you just created # Import the Space Export # On a page, create the Task Report Macro, and point it at the imported space. h5.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) h5.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. h5.Workaround (not applicable to Confluence Cloud) # Perform a full backup of the Confluence Database # Shutdown Confluence # Execute the following SQL Queries: {code:sql} delete from "AO_BAF3AA_AOINLINE_TASK"; delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build'; {code} # 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. h3. 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: {code} CATALINA_OPTS="-Dtasklist.storagetoaoupgradetask.numthreads=18 ${CATALINA_OPTS}" {code} To define the ideal number of threads for the process, we can use the following formula: {code} ideal_thread_number = availableProcessors() * 2 + 2; {code} |
| Remote Link | New: This issue links to "Page (Confluence)" [ 480370 ] |
| Description |
Original:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-34751]. {panel} h5.Steps to Reproduce # Create a new Space # Export the Space as XML # Delete the Space you just created # Import the Space Export # On a page, create the Task Report Macro, and point it at the imported space. h5.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) h5.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. h5.Workaround (not applicable to Confluence Cloud) # Perform a full backup of the Confluence Database # Shutdown Confluence # Execute the following SQL Queries: {code:sql} delete from "AO_BAF3AA_AOINLINE_TASK"; delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build'; {code} # 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. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-34751]. {panel} {panel:title=Fix description|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff} 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. {panel} h5.Steps to Reproduce # Create a new Space # Export the Space as XML # Delete the Space you just created # Import the Space Export # On a page, create the Task Report Macro, and point it at the imported space. h5.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) h5.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. h5.Workaround (not applicable to Confluence Cloud) # Perform a full backup of the Confluence Database # Shutdown Confluence # Execute the following SQL Queries: {code:sql} delete from "AO_BAF3AA_AOINLINE_TASK"; delete from bandana where bandanakey = 'com.atlassian.confluence.plugins.confluence-inline-tasks:build'; {code} # 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. |
We migrated spaces from Confluence Server 6.11.2 to another instance with same version and lost all tasks in the task reports and in User Avatar > Tasks.
I think this is this issue, correct?
Question: If we update Confluence on the migration target environment to >= 7.0.1, will the tasks re-appear "automatically"? Or do we have to apply the workaround? Thanks!
| Remote Link | New: This issue links to "Page (Confluence)" [ 455725 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 453710 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 452358 ] |
Hello daniel.hertrich.external, good question!
I just tested this issue to confirm the behavior, and unfortunately, just upgrading will not re-create the link to the Task Report macro.
That being said, since the data is in the XML file, we do not need to export another Space export from the source Confluence, and can just import the existing XML file.
Cheers,
Sattesh