Confluence Page Properties Report Multiple Rows May 2026

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.

Go to your parent (dashboard) page and:

Summary

Why multiple rows is requested

Behavior and constraints

Workarounds and patterns

  • Use Page Properties + structured lists and external processing

  • Multiple Page Properties tables per page (limited)

  • Use a dedicated app/plugin (recommended for scale)

  • Use Jira for item lists + Jira Issues macro

  • Implementation checklist (one-per-child approach)

    Tips and best practices

    Recommended next steps

    In Confluence, the Page Properties Report macro is designed to display exactly one row per source page

    . If a table inside a Page Properties macro has multiple data rows, the report will only pull the first one by default. Atlassian Community

    Depending on your goal, here is how to handle or fix "multiple rows": 1. How to get multiple rows from one page

    If you need to report on multiple distinct items from a single page, you must use a workaround:

    Page Properties Report Not Showing All - Atlassian Community

    Confluence Page Properties Report: How to Display Multiple Rows confluence page properties report multiple rows

    Confluence is a powerful collaboration platform that enables teams to create, share, and manage content. One of its most useful features is the Page Properties Report macro, which allows users to create a table that displays properties from multiple pages. However, one common limitation of this macro is that it only displays a single row of data. In this article, we'll explore how to display multiple rows in a Confluence Page Properties Report.

    What is a Confluence Page Properties Report?

    A Page Properties Report is a macro in Confluence that enables users to create a table that displays properties from multiple pages. This macro is useful for creating reports, dashboards, and other types of pages that require data from multiple sources. With a Page Properties Report, users can easily create a table that displays information such as page titles, authors, creation dates, and more.

    The Limitation: Single Row Display

    By default, the Page Properties Report macro only displays a single row of data. This can be limiting when you need to display data from multiple pages. For example, if you have a report that needs to display data from 10 different pages, you would need to create 10 separate Page Properties Report macros, each displaying a single row of data. This can be cumbersome and make your page look cluttered.

    Solution: Using the Page Properties Report with Multiple Rows

    So, how can you display multiple rows in a Confluence Page Properties Report? The solution involves using a combination of Confluence macros and some clever configuration. Here are the steps:

    Step 1: Create a Table on Each Page

    To display multiple rows in a Page Properties Report, you need to create a table on each page that contains the data you want to display. This table should have a single row with the properties you want to display. For example, if you want to display the page title, author, and creation date, your table might look like this:

    | Page Title | Author | Creation Date | | --- | --- | --- | | My Page | John Doe | 2022-01-01 |

    Step 2: Add the Page Properties Macro

    On each page, add the Page Properties macro to the table you created in Step 1. This macro will allow you to specify the properties that you want to display in the report.

    Step 3: Add the Page Properties Report Macro

    On the page where you want to display the report, add the Page Properties Report macro. This macro will allow you to specify the pages that you want to include in the report.

    Step 4: Configure the Page Properties Report Macro

    To display multiple rows in the report, you need to configure the Page Properties Report macro to use a specific layout. To do this, follow these steps:

    Step 5: Add Pages to the Report

    To add pages to the report, click the Add pages button and select the pages that you want to include. You can select multiple pages by holding down the Ctrl key (Windows) or Command key (Mac).

    Step 6: Save and View the Report

    Save the page and view the report. The Page Properties Report macro should now display multiple rows of data, one for each page that you selected. Parent Page: Risk Dashboard Child Pages: Risk 001,

    Tips and Variations

    Here are some tips and variations to help you get the most out of the Page Properties Report macro:

    Conclusion

    Displaying multiple rows in a Confluence Page Properties Report is a powerful way to create reports and dashboards that showcase data from multiple pages. By following the steps outlined in this article, you can create a report that displays multiple rows of data, making it easier to analyze and visualize your data. Whether you're a Confluence power user or just starting out, this article has provided you with the knowledge and skills to take your reporting to the next level.

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


    Title: The Case of the Missing Requirements

    Characters:

    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): Summary

    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.

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

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

    The “Multi-Row” Workaround:

    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:

    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:

    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:

    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.

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


    For organizations heavily reliant on this functionality, the native Confluence macros often fall short. This is one of the primary drivers for add-ons like Aura or Table Filter and Charts.

    These plugins often extend the functionality of tables, allowing for dynamic aggregation where a single page can spawn multiple rows in a summary report, bypassing the limitations of the native Page Properties macro logic.

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

    Labels are the most reliable way to filter Page Properties Reports. Example: status-in-progress, team-marketing.