Confluence Page Properties Report Multiple Rows -

Here’s a useful, real-world story about solving a tricky documentation problem in Confluence.

Title: The Case of the Missing Requirements

Characters:

• Alex – Technical Lead, pragmatic, hates manual updates.
• Jordan – QA Manager, detail-oriented, loves traceability.
• Sam – New project coordinator, eager to help.

The Situation:

Alex’s team was developing “Project Chimera,” a complex integration involving 15 microservices. Each service had a Confluence page detailing its API contracts, environment variables, and test cases. On every page, Alex used a Page Properties macro to store key metadata:

| Property | Value | |----------|-------| | Service Name | auth-gateway | | Owner | Platform Team | | Criticality | High | | Last API Review | 2025-02-10 |

The problem? Auditors and Jordan (QA) needed a single view of all services with their properties—without clicking into 15 pages. Alex knew about the Page Properties Report macro, which pulls property tables from multiple pages into one master table.

But here’s the catch: The report usually shows one row per page (each page’s properties in one row). Jordan needed multiple rows per page because some services had multiple critical environment variables, each requiring its own row for test tracking.

The Confusion:

Jordan tried to add multiple property rows inside a single page’s Page Properties macro, but the report still collapsed them into one row.

Example inside one page:

| Property | Value | |----------|-------| | Service Name | auth-gateway | | Env Var | AUTH_HOST | | Env Var | AUTH_PORT | | Env Var | AUTH_TIMEOUT |

The report showed:

| Service Name | Env Var | |--------------|---------| | auth-gateway | AUTH_HOST, AUTH_PORT, AUTH_TIMEOUT |

Not multiple rows. Unacceptable for test case mapping.

The Eureka Moment (How to achieve multiple rows per page):

Alex realized: The Page Properties Report treats each page as one row by default, merging all properties into that row. To get multiple rows from one page, you must split each data item into its own separate page – or use a different approach. confluence page properties report multiple rows

But creating 45 pages (3 env vars × 15 services) was overkill. Instead, Alex found a cleaner method:

1. Use the “Page Properties” macro for fixed metadata (service name, owner).
2. For multiple rows (e.g., environment variables), use a Table of Contents + Labels + Page Properties Report with label filtering.

But that’s still heavy. So Alex built a simpler trick:

The “Multi-Row” Workaround:

• 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.

But that’s still manual. For true elegance, Alex scripted a small automation (using Confluence API + Python) to generate those child pages from a spreadsheet.

The Solution in Practice:

Instead of fighting Confluence, Alex presented to Jordan:

“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.”

They agreed on a hybrid approach:

• Each service has a “master properties” page (one row in report).
• Each service also has a child page called “Environment Variables” – inside that page, they used Table Transformer macro (from marketplace add-on) to pivot a multi-row table into a view, but not for the report.

For the audit requirement, Jordan used Confluence SQL (via the official SQL for Confluence add-on) to query page properties across all pages and output true multiple rows per source page. Example query:

SELECT p.title AS service, cp.var_name, cp.var_value
FROM pages p, child_properties cp
WHERE p.id = cp.page_id AND cp.property_set = 'env-vars'

That produced:

| service | var_name | var_value | |---------------|--------------|----------------| | auth-gateway | AUTH_HOST | localhost | | auth-gateway | AUTH_PORT | 8080 | | auth-gateway | AUTH_TIMEOUT | 30s |

The Outcome:

• Audit passed – clear traceability.
• Jordan happy – multiple rows per logical service.
• Sam learned – “Page Properties Report shows one row per Confluence page, not one row per property.”

Key Takeaway for the Reader:

If you need multiple rows from the same Confluence page in a Page Properties Report, you can’t. The macro’s design is page-centric. Workarounds:

1. Split each row into its own child page – then report shows multiple rows.
2. Use an add-on (Table Transformer, SQL for Confluence, or ScriptRunner) to restructure data.
3. Export page properties via API and render your own multi-row table elsewhere (e.g., in a dashboard).

The Moral:
Confluence’s Page Properties Report is great for page-level summaries. For true row-level granularity, either design your page hierarchy around rows or bring in external tools. Alex’s team chose the API route and never looked back.

Confluence Page Properties Report: Displaying Multiple Rows Here’s a useful, real-world story about solving a

The Confluence Page Properties Report macro allows you to display metadata from a page in a table format. However, by default, it only displays a single row of data. If you want to display multiple rows of data, you can use the following approaches:

Method 1: Using the Confluence Page Properties Report macro with multiple page property macros

You can add multiple Page Property macros to a single page, each containing a different set of metadata. Then, use the Confluence Page Properties Report macro to display all the page properties.

Here's an example:

| Page Property Macro 1 | Page Property Macro 2 | ... | | --- | --- | ... | | Property 1: Value 1 | Property 2: Value 2 | ... | | Property 3: Value 3 | Property 4: Value 4 | ... |

Confluence Page Properties Report Macro

| Property | Value | | --- | --- | | Property 1 | Value 1 | | Property 2 | Value 2 | | Property 3 | Value 3 | | Property 4 | Value 4 |

Method 2: Using a Table Macro with multiple rows

Alternatively, you can use a Table macro to create a table with multiple rows. You can then use the Page Property macro to populate the table cells.

Here's an example:

Table Macro

| Property | Value | | --- | --- | | Property 1 | page-property:Property 1 | | Property 2 | page-property:Property 2 | | Property 3 | page-property:Property 3 | | Property 4 | page-property:Property 4 |

In this example, each row of the table displays a different set of metadata.

Method 3: Using a Third-Party Add-on

There are also third-party add-ons available that provide enhanced functionality for displaying multiple rows of data in a Confluence page properties report. One such add-on is the Advanced Page Properties add-on.

Advanced Page Properties Add-on

This add-on allows you to display multiple rows of data in a page properties report using a simple syntax.

Here's an example:

Advanced Page Properties Macro

| Property | Value | | --- | --- | | advanced-page-properties | | Property 1 | Value 1 | | Property 2 | Value 2 | | Property 3 | Value 3 | | Property 4 | Value 4 | | /advanced-page-properties |

This add-on provides a more flexible and customizable way to display multiple rows of data in a Confluence page properties report.

Conclusion

Displaying multiple rows of data in a Confluence page properties report can be achieved using various methods, including using multiple page property macros, a table macro, or a third-party add-on. Choose the method that best fits your needs and requirements.

Here’s a clear write-up explaining how to display multiple rows using the Page Properties Report macro in Confluence.

Method 4: The Power Solution – Confluence Database (Atlas – Beta/New Feature)

Atlassian recently introduced Confluence Databases (formerly Atlas, now rolling out as a native feature in premium plans). This is the true solution for multiple rows.

A Confluence Database is a structured table that lives on a Confluence page and supports:

• Multiple rows and columns
• Sorting, filtering, and linking to Jira
• Embedding in multiple pages
• Real-time collaboration

When to Use This vs. Other Tools

• Use Page Properties Report when you have 5–500 rows and want native, permission-controlled, searchable data without external databases.
• Use Table Filter macro (if licensed) for inline editing, pivots, and advanced filtering.
• Use Comala Databases for relational data, rollups, and complex formulas.

Example: Project Risk Register

Parent Page: Risk Dashboard
Child Pages: Risk 001, Risk 002, Risk 003 (each labeled project-risk)

| Page Title | Status | Owner | Due Date | Impact | |------------|--------|-------|----------|--------| | Risk 001 | Open | Alice | 2025-05-01 | High | | Risk 002 | In Progress | Bob | 2025-04-15 | Medium | | Risk 003 | Closed | Alice | 2025-03-30 | Low |

This table is generated automatically. Adding a fourth child page creates a fourth row instantly.

Method 5: Marketplace Add-Ons (For Serious Multi-Row Needs)

If you don’t have Premium or need advanced reporting, Atlassian Marketplace offers several apps that extend Page Properties:

2. Insert the Page Properties Report Macro

On a separate “dashboard” page:

• Type {page properties report and select the macro.
• In the macro parameters:
  • Label – Enter the common label you used (e.g., project-task).
  • Columns to show – Specify which columns from the Page Properties table to display (e.g., Status,Owner,Due Date). Leave blank to show all.

5. Consider migration to Databases.

If your team repeatedly asks “how do I add another row?” – you’ve outgrown Page Properties. Move to Confluence Databases or a dedicated tool like Jira Product Discovery. Title: The Case of the Missing Requirements Characters:

Overview

The Page Properties and Page Properties Report macros work together to create structured, table-like data across multiple pages.
When you want the report to show multiple rows (one row per labeled page), you need to set up your content correctly.