Commonly, users expect a one-to-one relationship: one page equals one row in a report. However, there are many scenarios where you need a single Confluence page to output to a report. Whether you are tracking multiple action items on one meeting note or listing several software requirements on a single specs page, here is how you master the "multiple rows" setup. The Fundamentals: How the Macros Talk to Each Other
In your Page Properties Report, you can now define columns for "Skill 1," "Skill 2," and "Skill 3." This ensures all data is captured and displayed on the single report row corresponding to John Doe’s page.
Contains the Page Properties macro. Inside this macro sits a standard Confluence table containing your metadata keys (columns) and values.
The obsession with "fixing" the multiple-row issue is often a sign that the knowledge worker is trying to force Confluence to become Jira, or Airtable, or SQL. confluence page properties report multiple rows
Why multiple rows is requested
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.
Confluence Page Properties Report: Mastering Multiple Rows and Data Visualization Commonly, users expect a one-to-one relationship: one page
For more robust reporting without manual restructuring, third-party apps provide specialized macros:
If you want the report to technically stay as one row but display a full list of items: Confluence page properties and page properties report.
If you put multiple rows in your source table inside the macro, Confluence typically ignores everything after the first row or merges them into a single cell. The Fundamentals: How the Macros Talk to Each
Jordan tried to add multiple property rows inside a single page’s Page Properties macro, but the report still collapsed them into one row.
This is the "one-to-many" relationship: one row in the report table corresponds to one source page. The result is a powerful, standardized way to create status reports, risk registers, product requirements, and decision logs.
| Problem | Likely Fix | |---------|-------------| | Only one row shows | Check that multiple pages actually have the and contain a Page Properties macro. | | Columns are missing | Ensure column names in Page Properties Edit macros match exactly across pages (case‑sensitive). | | No data appears | The report page must not have the same label as the data pages. |
Go to your parent (dashboard) page and:
The best practice is usually : Rename your rows to Item 1 , Item 2 , Item 3 . While this makes your source table slightly more verbose, it results in a robust, sortable report that captures all your data without requiring expensive add-ons or switching to the Task Report system.