We are using the Page Properties Report macro, which pulls in info from Page Properties macro info on other pages with certain labels.
Ours are labeled jirareport. However, the Page Properties Report macro is pulling in content from Page Properties macros that we don't want to show. To stop this, I relabeled those to jirasprintreport, but they still show on the report page. I used CQL to add a -jirasprintreport to try to force block it, and they still appear.
I'm wondering if this is a bug, or if I'm misunderstanding how the macros work? Or if there are hidden labels I'm not seeing?
Hello @Kri Dontje !
As I understand, using the Page Properties Report macro does not work as expected when displaying contents based on labels.
I tried to replicate this outcome by doing the following:
- Created a page
- Placed a Page Properties macro
- Published the page
- Added the label called “label” to the page
- Created another page
- Placed a Page Properties macro
- Published the page
- Added the label called “anotherlabel” to the page
- Create a third page
- Placed the Page Properties Report macro
- Limited the displayed content to pages with the label called “label”
- Published the page
- The report macro displays solely the page that contains the label
With these results at hand, I would like to ask a few questions:
- Has this worked at some point in the past?
- Do you pages contain multiple labels?
- Is this behavior present if you specify any other label in the Page Properties report macro?
Let us hear from you!
Figured it out! I was looking at the ID you can add to the Page Properties macro itself, rather than at the label attached to the Confluence page. Thank you for the screenshots, where I could see that, when I'd overlooked it hiding at the bottom of very long pages in our system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great to know you got it work the way you need it to.
Come share with the community sometime in the future!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.