In the page restrictions or page settings, add a unique label to every child page (e.g., project-tracking-2026 ). Step 3: Configure the Report Macro Navigate to your master overview page. Insert the .
Mastering the Confluence Page Properties Report with Multiple Rows
In the field, enter the label you used on your child pages (e.g., project-status ).
Assign unique IDs to Page Properties macros if you have multiple on one page to avoid data confusion. confluence page properties report multiple rows
The fundamental issue stems from a design choice in Atlassian's macro architecture: Each page in your report corresponds to a single Page Properties macro instance. If you place multiple tables or rows within a single Page Properties macro, the report will only capture the first one.
Create a single "template" page that contains the . Inside this macro, define your columns using tables or labeled lists .
If you want a single Page Properties Report to display multiple rows of data from a single source page, you must structure your data correctly. Confluence generates one row in the report for every it finds on a page, provided those macros have unique ID attributes. In the page restrictions or page settings, add
Example of three child pages:
This is the critical step that forces Confluence to treat this macro as an independent row. Click on the Page Properties macro frame.
You can then use the . This macro creates a one-to-many relationship naturally. One page (John Doe) can spawn multiple rows in the report (one for each task). If you place multiple tables or rows within
If you want a Page Properties Report to display 10 distinct rows of data, the native, intended way to achieve this in Confluence is to .
If you use multiple Page Properties macros on one page without specifying unique IDs, Confluence will get confused. It will either overwrite the data, display only the first table, or bunch all the text into a single row cell. Always use unique IDs if keeping data on one page. 3. Missing Rows in the Report
macro, the report will generally only display the first row of that table Atlassian Community
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.
The standard Page Properties macro is primarily designed to handle "key-value pairs" (like "Status: In Progress"), resulting in a single row per page in your final report. However, there are a few clever ways to bypass this limitation and display multiple rows from a single page in your report. 1. The Native Hack: Multiple Macros with Unique IDs