Confluence sometimes crashes or fails to render nested macros. Keep them at the same level.
By default, the report is designed to show one row per page. But, with the right structure—specifically using the or clever nested macros—you can display multiple rows per page, allowing for advanced reporting on tasks, requirements, or data subsets. What are Page Properties and Page Properties Report?
Instead of storing multiple rows of data on a single page, create . For example, if you are tracking five project risks, create five separate pages, each containing its own Page Properties macro with the same label. The report macro will then show all five pages as five rows in the output table.
One page + One Page Properties macro = One row in the report.
Before we solve the problem, let’s clarify the default behavior. confluence page properties report multiple rows
Duplicated rows in page properties report - Atlassian Community
Displaying all these as individual rows in the master report—rather than just one row representing the entire page—allows for and better filtering in the master table. Method 1: The "Nested Table" Technique (Native Method)
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).
Note: The Page Properties Report will treat each property name as a separate column. Confluence sometimes crashes or fails to render nested
By creating multiple child pages, each with its own Page Properties macro, the Report macro will automatically generate in a table—one row per child page.
def response = new JsonSlurper().parse(apiUrl, 'GET', query)
Look for the Page Properties ID field in the report settings. Leave this field completely blank . Leaving it blank tells the report to pull all Page Properties macros from the labeled pages, rather than filtering for just one specific ID.
Workarounds and patterns
However, a common question arises when teams need to track more than just one row of data per page: “Can the Page Properties Report show multiple rows?”
The macro generates a where:
If you have multiple Page Properties macros on one page or a multi-row table inside a single macro, the standard report macro often fails to treat them as separate rows, instead merging them into one entry or only displaying the first one. Method 1: The Multiple Macro "ID" Workaround
Use SQL-like queries to restructure the data, expanding nested lists into individual rows. Best Practices for Multiple Row Reports But, with the right structure—specifically using the or
In the field, type the exact names of the keys from your left-hand table columns (e.g., Status, Owner, Due Date ), separated by commas. Click Save and Publish the page.