Page properties report label from template/blueprint variable

[Dries De Backker]

Hello,

Within our software engineering team, we are going to document our applications in Confluence. For that purpose, we have developed a template. The template includes a series of page properties reports, e.g. documents, meetings, projects... for pages of that type that are associated to the application. Now, when creating a new application page from this template, the author still has to set the label (which is just documents-applicationname, meetings-applicationname....) manually for each report macro.

Is there a way to fill in the labels of page properties reports automatically based on a variable in a template or blueprint?

Thanks!

[Dea Mandija · Accepted solution]

Hello @Dries De Backker ,

I am not aware if there is any workaround within Confluence to automatically fill in the labels of the page properties report, maybe someone has a better answer to that.

On the other hand, there are multiple applications available on the marketplace that can help you manage metadata related to your content (and can solve your issue):

https://marketplace.atlassian.com/search?product=confluence&query=Metadata

Are you currently using the cloud or server version for Confluence?

Either way, Metadata for Confluence could be a good option since it handles both. I'm part of the team behind it :) 

Hope this helps!

Regards, Dea. 

[Dries De Backker]

Dear Dea,

Thank you for the suggestion!

I've looked into the documentation of Metadata for Confluence. Using the macro Content by Metadata, it seems to be possible to filter pages based on the title of the page. This makes it possible to place tables on the template of application pages that display all the associated pages of a certain metadata type that include the application name in a certain field. 

However, I can't make out if this also applies if the field is a list of applications, which is one of our requirements. When using labels, this is of course no problem.

Anyway, we cannot choose our Confluence add-ons ourselves at the moment, but I will keep this suggestion in mind should the opportunity arise.  I'm still kind of hoping that in the future, blueprint variables can be directly used as macro parameters in vanilla Confluence ;-)

Regards, Dries