Confluence Page Properties Report Multiple Rows Instant

Small, stable datasets (e.g., 3–5 rows per page) where you control all content.

When you run the Page Properties Report on your parent page, it will automatically generate one row for every child page, creating a clean, automated multi-row list. Troubleshooting Common Row Issues Page Properties Report Macro | Confluence Data Center 10.2

If you only need the appearance of multiple rows within a single page's report entry, and you do not need to sort or filter those sub-rows individually, you can use a formatting trick inside a native Page Properties macro. On your child page, open your macro table.

To get multiple rows for one page in your report, you can add multiple macros to that page. confluence page properties report multiple rows

Confluence allows you to place multiple macros on a single page. If you have three separate Page Properties macros on "Page A," the Page Properties Report will display three distinct rows for "Page A."

In the left column, list your metrics (e.g., Status, Owner, Due Date). These are your keys.

def reportHtml = '<table>' reportData.each row -> reportHtml += '<tr>' reportHtml += "<td>$row.title</td>" reportHtml += "<td>$row.author</td>" reportHtml += "<td>$row.creationDate</td>" reportHtml += '</tr>' Small, stable datasets (e

Use a : Give every child page a consistent label (e.g., project-status ) to ensure the report can find them.

18;write_to_target_document1a;_ciPuabL2OOfP2roP5bu40A0_20;56; 0;aea;0;407;

By design, the Page Properties macro uses a to store key-value metadata (e.g., "Status → In Progress", "Owner → John"). When you embed multiple rows of data within a single Page Properties macro—such as a list of several risks or a table of tasks—the Page Properties Report macro will only output the very first row from that page. On your child page, open your macro table

Duplicated rows in page properties report - Atlassian Community

The simplest way to get multiple rows in a report without third-party apps is to use multiple Page Properties macros on your source page. How it works:

Placing complex macros (such as Jira Issue macros) inside a Page Properties macro can cause the report to break or show blank content. The report macro may not be able to render nested content correctly.