Here’s a clear write-up explaining how to display multiple rows using the Page Properties Report macro in Confluence.
Decide on a unique label to group your data pages. For example, if you are tracking project risks, use the label risk-item. This ensures the Report macro only pulls the correct pages.
The Confluence Page Properties Report macro is one of the most powerful tools for project management and tracking. It allows teams to aggregate data from multiple child pages into a single "master" view. However, users often encounter a specific structural limitation: how to handle scenarios where a single page contains multiple rows of data. confluence page properties report multiple rows
If you have ever tried to report on a table inside a Page Properties macro that has more than one row, you know the frustration. By default, the Page Properties Report is designed to extract only the first row of data it finds. This creates a flat, one-to-one relationship between the page and the report entry.
So, how do you manage "one-to-many" data relationships? Below we explore the problem, the workarounds, and best practices. Here’s a clear write-up explaining how to display
If your data is truly dynamic—meaning you don't know if there will be 3 rows or 30—and a "flat" structure isn't feasible, the Page Properties macro may be the wrong tool for the job.
In this case, you should pivot to using Confluence Tasks. Step 1: Create a Labeling Strategy Decide on
Instead of a table inside a Page Properties macro, have users create Task items (using the [] checkbox syntax) on their pages.
You can then use the Task Report Macro. This macro creates a one-to-many relationship naturally. One page (John Doe) can spawn multiple rows in the report (one for each task).
Pros:
Cons: