3 answers
What you described seems like a common issue with the native Page Properties macro. Using it will get you part of the way there, but you'll likely hit some frictions, like the ugly property report.
I have a solution for you if you're open to marketplace apps. Full disclosure: I am affiliated with the team behind the app, but I genuinely recommend having a look at Properties, as it solves the problem you have.
With Properties, you define a Property Group, and apply it across all the pages you want to index. In your case, each page would get the same consistent set of 20 fields. You can then place a Property Report on any page (or multiple pages) and have it pull from exactly the pages you specify, regardless of where they sit in the hierarchy. You can also update a field value directly in the report without opening each individual page, allowing for a real-time sync.
Since you want the report embedded in each Confluence page, that works too: you can place a Property Report macro on a page and scope it however you need — all pages in a space, a specific subtree, pages with a certain label, or even pages across different spaces.
Here is an example of the report automatically created with Properties:
If you have any question or if you'd like to see it in action - I'm here to help.
Hi, @Michael Pfannkuchen,
In this case, a custom use macro can do the thing. I've been experimenting with our app and managed to achieve a good result.
Actually, the solution is pretty customizable and can be adjusted to meet your requirements. Here's a ready-to-use template.
Please let me know if this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.