Need help with multi project follow up table

[Ivo Ooghe]

Our marketing department uses a separate Confluence task follow up page per individual project.

These pages all have a generic layout with as most important element a Scaffolding table containing headers that are identical on all project pages.

Some of the headers are category, phase, description, owner, duedate, workload(h) and %complete.

The challenge is that we wish to report on all of the separate project follow up pages and tables and be able to retrieve the following overall information:

- All tasks for a given category

- All tasks for a specific owner

- Calculate workload per week per owner (duedate field is now a date field but could be changed to numeric weeknumber if needed)

I have tried the following approaches but failed:

- Page properties report on parent page and page properties on childs only retrieves the first row (using repeating data on the child pages does not seem fix this problem)

- Pivot table on the parent page, filled with Excerpt includes and Excerpts filled with a table data macro -> comes close but the Pivot table representation is incomprehensible with larger amounts of data

- Using Report table works on the child page but on the parent page the text, number, date, evaluate data fields don't seem to be visible - putting the table on the child in an Excerpt and using a Local reporter with excerpt on the parent fails - with a content reporter it produces multiple blank lines but no result

- Working with Get Data seems to be restricted to one page (data fields from child pages don't seem to be visible on the parent) and when using this in conjunction with table data, one needs to refer to every row of the source table explicitly (e.g. Tasks.2.Owner to retrieve the Owner from the third row) which is not manageable given the large amount of child pages and tables.

Is this even possible in Confluence + Scaffolding & Reporting (or any other useful addons)?

Any help is greatly appreciated!

[Ivo Ooghe · Accepted solution]

Problem solved using a report table with an expanding reporter using a content reporter of the type page, using > descendents.

Within the report column one can use the report info column with expanded:[expanding reporter name]>data:variable_name.