Here's an example:
This one-row-per-page behavior is intentional: the macro is designed to surface atomic metadata assigned to a page, not to aggregate full tables stored within that page. Consequently, if you add ten issues to a Page Properties table on one page, only one appears in your report.
Label all child pages with a specific tag, such as inventory-item . Step 2: Report on the Parent Page
| service | var_name | var_value | |---------------|--------------|----------------| | auth-gateway | AUTH_HOST | localhost | | auth-gateway | AUTH_PORT | 8080 | | auth-gateway | AUTH_TIMEOUT | 30s | confluence page properties report multiple rows
I can provide specific macros or plugin recommendations based on your environment. Share public link
“We cannot force one page to produce multiple rows in a Page Properties Report. The macro was built for page-level aggregates. To get multiple rows, each row must be its own page.”
Follow these exact steps to build a functional tracking dashboard that outputs multiple rows. Step 1: Create the Master Label Step 2: Report on the Parent Page |
when you must keep multiple rows on a single page but can tolerate managing separate macros per row.
If your team needs to report on large, dynamic tables with many rows, the native macro often falls short. Many Atlassian Community members recommend the Table Filter and Charts for Confluence The Macro: Table Excerpt Table Excerpt Include The Benefit:
By default, the report lists each as a single row. If you need a single page to contribute multiple rows to a report, follow these steps: 1. Use Multiple Page Properties Macros To get multiple rows, each row must be its own page
This article explains how to set up a "master-detail" system where child pages feed data into a single, sortable report on a parent page.
Edit this second macro and set a different (e.g., row-2 ). Add your second set of table data.
Example of three child pages: