Some confluence pages with the "requirements" label do not appear in a page properties report configured to show all pages with the requirements label.
Eg, Page A and B have a page properties macro instance on them (with say fields field_a, field_b) and the "requirements" label applied. Page C has a Page Properties Report macro configured to show properties from pages with the "requirements" label. Surprisingly Page A and its fields do not appear in the page properties report, whereas Page B does. Perhaps more surprisingly, deleting the requirements label on Page A and re-applying it clears the problem (now both pages show up in the page properties report). Persistent issue is figuring out how pages get into this non-working state.
Using the Confluence GUI, pages that aren't showing up in the page properties report do have the requirements label at their bottom right as expected. Using the REST API also shows that the pages in question have the requirements label. Also using the REST API to expand the page content shows that the CQL field driving the page properties report has a query of the form (eg, lablel="requirements" and name ~ XXX").
Searching for pages labelled with "Requirements" doesn't produce the problematic pages when the page properties macro is not working for them - but as noted above the labels appear on those pages when viewed through the GUI.
Can't think of a reason why seemingly replacing the existing "requirements" label with itself on the page fixes the issue, nor why it occurs in the first place.
Any suggestions welcome :-)
I know this is an old issue, but I thought I'd drop some breadcrumbs for the next person to see this page.
This might be caused by a problem with Confluence's search index. One way to fix it is to rebuild the search index.
If removing and reapplying the label fixed it, perhaps this behaviour is enough for your search index to catch up and "notice" the page.
Also having a similar issue. The pages clearly show the label but are not showing up in the page properties report. Simply editing the page, CHANGING NOTHING and publishing is enough to cause them to show up in the report. This is problematic for us as we're using this macro to collect release documents and sometimes they just don't show up, then we have to go modify each page to get them to display in the report. Requires a manual workaround which this report is supposed to help replace.
We have the same problem, but we only have to view a missing page for it to start appearing in the report. Slightly easier, but unfortunately, that means manually visiting 350+ pages every time we refresh that catalog, so still not a great (admin) user experience.
Anyone know if the Confluence team is working on this bug?
This is really annoying issue.
I have even tried to add a completely new label and build a new properties report and seems like confluence completely ignores those absent pages even in the new report, though other pages when adding this new label are shown in the report instantly.
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events