Confluence Page Properties Report Multiple Rows ✨

Mastering the Confluence Page Properties Report for Multiple Rows

| Problem | Likely Cause | Fix | |---------|--------------|-----| | No rows appear | Wrong label or parent page | Check label spelling; ensure child pages are descendants | | Columns missing or misaligned | Inconsistent property names | Use the exact same property names in every Page Properties macro | | Values not updating | Confluence cache | Refresh the page; clear browser cache | | Extra empty rows | Pages with the label but no Page Properties macro | Remove label from those pages |

To avoid issues with multiple rows in your Page Properties Report:

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

: Place each row of data into its own individual Page Properties macro on the source page.

Data that is naturally page-centric (e.g., individual meeting notes, product requirements).

In the macro settings, restrict the report to the label project-task . Save the page. Mastering the Confluence Page Properties Report for Multiple

Whichever method you choose, follow these rules to avoid chaos:

The report will now automatically crawl every page bearing that label and display them as in your master table.

But creating 45 pages (3 env vars × 15 services) was overkill. Instead, Alex found a cleaner method: In the macro settings, restrict the report to

What (e.g., tasks, risks, metrics) are you trying to organize? Share public link

pages.each page -> def metadata = page.metadata def rowData = [ title: page.title, author: metadata.author, creationDate: metadata.creationDate ] reportData << rowData

user wants a long article about "confluence page properties report multiple rows". I need to provide comprehensive guidance on managing multiple rows in Confluence Page Properties Report macros. The search results cover key aspects: limitations of built-in features, workarounds using multiple Page Properties macros, indexing each row, using the Table Filter and Charts for Confluence app (which is critical for multi-row reports), and other related apps like Refined for Confluence, Better Content Archiving, etc. The Atlassian documentation explains the basics of Page Properties and Page Properties Report macros. The workaround article suggests adding an "Order" property to index rows. The Table Filter and Charts user guide explains how to combine page properties tables from multiple pages into a single view, which is exactly what's needed for multi-row reports. I will structure the article to cover the challenge, the hidden index technique, using Table Filter and Charts for dynamic multi-page reports, best practices, limitations, and troubleshooting. I'll cite the sources appropriately. have gathered information from various sources. Now I need to synthesize a comprehensive article on "confluence page properties report multiple rows". The article should cover the inherent limitations, workarounds like using multiple Page Properties macros, indexing with an 'Order' property, and the recommended approach using Table Excerpt/Table Excerpt Include and Table Transformer macros from the Table Filter and Charts app. I will also discuss best practices, limitations, and troubleshooting. I will cite the sources appropriately. Mastering Multi-Row Reports: A Complete Guide to Confluence Page Properties Report