If you are just starting, try the first. If you need advanced data manipulation, explore the Atlassian Marketplace for filtering tools to take your reporting to the next level. *If you’d like, I can: Show you step-by-step screenshots of how to set this up. Give you a sample SQL query for the Table Transformer app. Compare the top 3 apps for advanced Confluence reporting.*
On the overview page, insert the macro. Set the label filter to project-task-item . Because every individual item now lives on its own child page, the report will naturally display each item as its own distinct row.
By design, the Page Properties macro captures "key-value" pairs intended to summarize a specific page (e.g., Status: Active, Owner: Sarah). When the runs, it looks for pages with a specific label and creates one row for each page it finds.
Placed on a single master page (e.g., a team dashboard). It searches your space, pulls the data from those individual child pages, and displays them as a multi-row table. confluence page properties report multiple rows
Before diving into multiple rows, let’s define the basics:
So, how do you manage "one-to-many" data relationships? Below we explore the problem, the workarounds, and best practices.
Follow this workflow to build a functional, multi-row dashboard for tracking items like project statuses or team objectives. Step 1: Create a Blueprint or Template Page If you are just starting, try the first
When you run the Page Properties Report on your parent page, it will automatically generate one row for every child page, creating a clean, automated multi-row list. Troubleshooting Common Row Issues Page Properties Report Macro | Confluence Data Center 10.2
A Confluence Database is a structured table that lives on a Confluence page and supports:
If you’ve tried the above and still see only one row per page, check: Give you a sample SQL query for the Table Transformer app
In the macro configuration sidebar, type your label ( project-status ) into the field. Click Insert or Save . Publish the page.
Create one "Parent" page for your project and individual "Child" pages for each item or task. Execution: Place a single Page Properties macro on every child page.