PropPulse for Confluence
A better Page Properties Report: column widths, page status, sorting, filtering, grouping, paging and Excel export. By PuzariCloud. Runs on Atlassian.
What it does
PropPulse adds the Page Properties Report+ macro. Like the built-in Page Properties Report, it collects the Page Properties macros from many pages into one table, one row per page. You keep your existing Page Properties macros and labels; PropPulse only reads them.
On top of the native report it adds:
- Column widths: set a width for any column, or drag a column edge in the editor preview.
- Columns you control: every property key is discovered automatically; show, hide, rename and reorder columns.
- Page fields: page status (the content status shown next to the page title), created, last modified and space.
- Sort by any column (dates and numbers sort correctly, empty cells stay last), filter as you type and group by any column.
- Paging with 10 to 200 rows per page, over up to 2,000 pages per report.
- Export to CSV or Excel (.xlsx), and a real table in Confluence PDF and Word exports.
- Light and dark themes, keyboard accessible.
Add a report
- Edit a page, type
/Page Properties Report+ (or open the + menu and search for PropPulse) and insert the macro.
- Choose the pages:
- Labels: one or more labels, matching pages with any or all of them, in this space, specific spaces or all spaces. This is how the native report works.
- CQL query: any Confluence Query Language filter, for example
space = DOC AND label = "decision" AND lastmodified > now("-90d"). PropPulse adds type = page. An ORDER BY clause decides which pages are read first when the result is larger than the scan limit.
- Optional: enter a Page Properties ID to read only the Page Properties macros with that ID, like the native report.
- The preview lists the matching pages and every property key it finds. Under Columns, tick the columns to show, type a new title, set a width in pixels (empty means automatic) and use the arrows to reorder.
- Under Display, pick the default sort, an optional grouping and the rows per page, and whether readers get the filter box and the export buttons.
- Click Save and publish the page.
Reading a report
- Click a column title to sort; click again to reverse. Use Tab and Enter to sort with the keyboard.
- Type in Filter rows to show only rows that contain every word you type.
- Use Group by to group rows by a column, for example by owner or status.
- CSV and Excel download the rows you see (after filtering), in the current sort order.
- Drag a column edge to resize it for yourself, or focus the edge and press the left and right arrow keys. Only the macro editor saves widths for everyone.
What is shown in cells
Status lozenges keep their colour, mentions show the person's current name, dates appear as YYYY-MM-DD and sort as dates, links stay clickable, lists and task lists keep one item per line. Other macros inside a cell show as plain text where possible. When a page has several Page Properties macros, the first value for each key is used.
Limits
- Up to 2,000 matching pages per report (default 500, set under Pages to scan). Larger reports show a notice; narrow the query or raise the limit.
- Pages only (not blog posts), as in the native report.
- Page status needs one extra request per page, so it is read only when that column, sort or grouping is used.
- PDF and Word exports include up to 500 rows, without grouping.
- Readers only see pages they have permission to view; restricted pages are left out for them.
Moving from the native Page Properties Report
Nothing to migrate. Your Page Properties macros and labels stay as they are. Insert Page Properties Report+ next to the native report, enter the same labels (and the same ID, if you use one), check the preview, then remove the native report. Both can sit on the same page while you compare.
Coming from a Connect metadata app, such as Document Metadata? Those apps keep their own metadata model; PropPulse reports on the standard Page Properties macro, which survives app changes and needs no app to edit.
Security and data
PropPulse runs on Atlassian Forge and is eligible for Runs on Atlassian. Reports are read with the viewer's own Confluence permissions and built in the browser. Report settings live in the macro on the page. The app stores no data of its own, keeps no personal data and makes no calls outside Atlassian. See the privacy policy.
Support
Email support@puzaricloud.in. We reply within two business days.