-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.7, 5.7.1, 5.9.7, 6.1.2, 7.12.2, 7.19.17, 8.5.7
-
30
-
Severity 3 - Minor
-
6
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Steps to reproduce:
- Create a Space
- Create Tasks on any page in Confluence
- Create a page with the Task Report Macro and filter the report based on Space and Page to populate the Task.
- Export the Space to XML.
- Import the Space to the New Confluence instance.
Expected
Task report macro recognizes tasks in the imported Space in the New Confluence instance.
Actual
Task report displays a message "Looking good, no incomplete tasks." in the imported Space in the New Confluence instance
Workaround
Option-1
The workaround discussed in Certain tasks do not show up in the Task Report Macro works for when the macro uses the Space Key as the identifier, but not when the macro uses Page ID.
Option-2
To populate the task reference the Page ID, manually edit the Task Report Macro from the imported Space, and find the page where the task exists.
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-
[CONFSERVER-37001] Task Report Macro is blank after importing space/site
Still an issue in 7.19.2.
The workaround suggested in https://confluence.atlassian.com/confkb/certain-tasks-do-not-show-up-in-the-task-report-macro-658179671.html is not suitable as we can't be taking our instance offline every time we need to import a space containing the task report macro.
Found the answer. There is a KB article about this situation. Atlassian does have a process to automatically populate the AO_BAF3AA_AOINLINE_TASK table.
We are experiencing this exact same problem after migrating 23 spaces from Confluence 5.9.7 server to a fresh Confluence 5.9.7 server.
The Task Report macro is no longer able to display the existing tasks. The tasks all must be recreated and the date picker also recreated for each task.
Same issue in 9.3.1 after Cloud to DC Migration