In Confluence, the Page Properties Report is natively designed to display one row per page. If you need to report on multiple rows from a single source page, you must use specific workarounds, as the macro typically only pulls the first row of data it finds. Option 1: Native "Multiple Macros" Workaround

Strategy 4: Formatting Workarounds (The "Cheats")

If you absolutely must use the native Page Properties macro and cannot flatten your data, some users employ visual cheats, though these are unstable.

Page A (Design homepage)
| Status | Owner | Due Date | |--------|-------|----------| | Done | Alice | Jan 10 |

Cons:

But when we need multiple rows where we see one, we are forced to admit defeat. We must acknowledge that the "Page" is too heavy a unit of measurement for granular data. We must migrate that data to a system where the "row" is the atomic unit, not the page.

• Create one parent page per service (e.g., “auth-gateway”).
• Inside that parent, create child pages for each variable/requirement (e.g., “Env: AUTH_HOST”, “Env: AUTH_PORT”).
• On each child page, insert a Page Properties macro with two properties:
  Service Parent = auth-gateway
Variable Name = AUTH_HOST (or PORT, TIMEOUT)
  Variable Value = actual value
• Then, on a master page, use Page Properties Report with Space and optionally Label filters. It will show one row per child page – achieving multiple rows logically grouped by service.