If that helps, I can reproduce this issue at will using 7.4.0.

I had 6 pages with the Page Property macro which contained a table such as

Looking at the page source, the header / grey cells were using <TH></TH> html tags. I wanted this for visibility, and to have the table in the page looked better this way. Unfortunately this seems to be messing up the Page Property Report

I had to edit all tables to remove all headings and have a dull and monotone table as such.

That fixed the Page Property Report page.

Chiming in again with a solution. Our problem seems to be that there were terminated users or (Unknown User @xxxxx) tagged on the page in question. Removing them seemed to make the page properties content show up in the page properties reports macro.

Just chiming in from 2021 this issue is still present on Server v7.12.4.

It is not solved

This bug has been resolved as fixed. If you believe that this bug is still affecting you then please contact support to verify the issue tht you are having. They will help to reproduce/diagnose and have the bug re-opened as necessary.

I am trying to understand how a very much persistent bug has been closed while not being fixed. We regularly rebuild our index from scratch but we can't be doing this regularly.

Can this be updated accordingly as it is still a bug in 6.6.4

Thanks

Still happening in 6.7.2

Hello,

we face multiple page issue on version 6.3.3

Apart from increasing the "number of items on display"as a workaound, will a permanent solution be released by Atlassian?

Regards,

Katerina

I have multiple rows on each child page that all need to be displayed in the compiled table on the final page.
Is there a possibility that the Page Properties macro can display more than one row/column from each page after the header? Currently it is selecting only the first matching row.

Is there a possibility that the Page Properties macro can display more than one row/column from each page after the header? I have multiple rows on each child page that all need to be displayed in the compiled table on the parent page.

We experience a problem with Confluence 6.3.1. We use multiple Page properties macro in pages. It works for some reports where only one page property is used, however for other reports, where multiple page properties are used, it displays 3 lines for the same system. The meta data displayed varies on the duplicated lines. 

What finally fixed it for us was rebuilding the search index from scratch.  This has to be done by the system administrators, not using the admin options inside Confluence.  You can get temporary relief by re-indexing using the admin tool for indexing, but you have to do that every time you change a label.

so get them to rebuild the index from scratch and see what happens.

Hi,
I'm experiencing this issue. We are using Confluence 6.0.7

My problem with it is that if I change the page label, the page is still reported under its original page label.  Or under neither the original nor the new page label.

Same if I use an ID instead of a page label.  

I'm using the page properties report, but it works sporadically. When initially set it up, it worked fine, but subsequent new pages (with the page properties and all labels the same) do not show. Please take a look. It's a valuable macro when working. 

I am also experiencing this issue.

Hello,

I have problem with Page Properties Report and Progress bar macro.
On preview it looks OK, but on save/update it is not showing right.

Can anyone help me?

Att:
https://goo.gl/gHy92H

–
Kruno

Hi there,

This bug or something similar to it exists on the Cloud version of Confluence. Can you please fix it asap?!

I get unpredictable results when I use Page Properties Report; too often now, I get no results. I have some examples where I get some but not all records and still other examples where (for now anyway) I seem to get all records that I should get.

In the meantime while you look into this to fix it for the Cloud, is it possible for me to directly write the JQL/CQL statement? I suspect that would work if the edited page would take my code. I am looking into that now.

Any idea when a fix for Confluence Cloud will be available?

Dear david.shaw63848008,

Thanks for raising this issue. I believe this is something that our support team will be able to help you with.
Could I ask that you create a support ticket on https://support.atlassian.com?
Once you've done this one of our support engineers will be in touch to work with you in resolving this problem.

Regards,
Minh Tran
Confluence Bugmaster
Atlassian

We have upgraded to the version just released (6.0.2) and are seeing two new bugs:  1.  Our page properties report was correctly showing a Comala State/Status. After the update the Comala statuses are now no longer showing up.   2.  Our JIRA tickets are throwing a security error: "JIRA Project Doesn't or you don't have permission" 

A fix for this issue is now available for Confluence Server customers.

Upgrade now or check out the Release Notes to see what other issues are resolved.

Therefore we hope that you do not need 6 month to release this medium rated bugfix.

Hmmm..., Atlassian is great on inceasing the Price every year -
but icredible sluggish to fix such annyoing and probably easy bugs.

I'm pretty sure there was no real reason you needed 2.5 years to fix this one.

As a paing customer - on time! - we expect a professional support which solves problems. (This bug is just one of many examples )

the occurrence factor is the likelihood of a user coming across this issue, not the likelihood that the bug will occur when following the steps to reproduce. i.e. it is likely to effect 10% of users.

"10% - edge case or very hard to experience"???

Running 5.10.0, any page that has more than one page properties macro on it has only the first macro's content displayed in a report. This is 100% of the time and is easily replicated.

+1

@Adam Barnes - "10% - edge case or very hard to experience"

Hardly. It happens 100% of the time using this, and it's not "very hard to experience" - it's pretty much every page that I use. I've had to create SO many extraneous pages for very little content because I cannot report on multiple page properties with different IDs on a single page.

Is there any other workaround apart from creating many pages ?

Any updates on ETA of this issue, it is quite annoying issue.

Any updates on an ETA for these fixes. The bug preventing the page properties report from including multiple page properties from the same page is a BIG impediment. I'm needing it to work per the documentation https://confluence.atlassian.com/doc/page-properties-macro-184550024.html ("You can add multiple Page Properties macros on a single page, and choose whether to include all or only specific macros in the report."). This is having a real impact on our ability to report status across a large project team. The bug CONF-34141 is over two years old. ...

Still having the issue in 5.10.5

I tried to do a custom macro "Page Properties Report" but It's difficult to read the content of the page...

I need help, here the code :

1. 1. @param filter:title=Filter|type=string|required=false|desc=Label filter

1. 1. Get all pages in the current Space
      #set ( $allPagesInSpace = $pageManager.getPages($space, true) )

1. 1. Loop through all pages in the current Space
      #foreach ($page in $allPagesInSpace)

#foreach ($label in $page.labels)
#set($label = "$label")
#if($label.contains("$paramfilter"))

<li>#contentLink2($content.getParent() false false)</li>
<li>#contentLink2($page.getParent() false false)</li>
<li>#contentLink2($page false false)</li>
<ac:structured-macro ac:name="get-metadata">
<ac:parameter ac:name="name">Source</ac:parameter>
</ac:structured-macro>

#end
#end

#end

1. 1. End looping through pages

Is there an update to this? I'm having to make some crazy workarounds to try and display data in this way- such as creating trees of individual pages that JUST contain the information I need in the properties report, as the data for the documentation surrounding those page properties shouldn't/isn't large enough to need individual pages - just sections of a page. It is creating a lot of manual overhead and is very painful.

Team,can you Please check if version 5.7.3 is affected too, i am able replicate it here. Thank you !

Guys, it is really not serious that for almost every bug we report to you, you keep saying "sorry, we are facing a known bug". Well, doesn't help me. If you want us to keep using your software, you have to start solve your bugs. Your software create many issues that cost as a month double than your software license. The other two common answer we get is "we need to re-index your instance" or "we need to restart your instance". Software is a serious business and I think that you should take it seriously.

When are you going to fix this bug which was already reported as fixed in one of the older version and apparently wan't?

We just wanted to build a business use case based on this feature (having multiple Page Properties macros on a page). Unfortunately, this will now fail.

Please provide a fix for this in the near future!

trudy.claspill this bug is currently under Tech Review, which means it's still being worked on. I have updated the Affects Versions to include 5.8 and 5.9. When it is resolved, the version that contains the fix will be listed in Fix Version.

Is there a version where it is proven that this functionality actually works as documented? This bug report says this is a problem all the way up to 5.7.1. I know that isn't the latest version, but all the documentation for the listed versions says this works when it actually doesn't. That diminishes my faith that it works in any version beyond 5.7.1.

We will be considering an upgrade to a newer version in the not too distant future. It would be good to know in which version this functionality actually works when we are deciding to which version we will upgrade.

Thanks

This has also become a major issue for our organization, in that we would like to have a page that contains multiple page properties and appear multiple times in a report (IE the page will have multiple presentation decks and each deck has its own page property report with a quick name/summary). However, the report will only pull 1 result even though the documentation states otherwise.

This used to function correctly in our instance until we upgraded, and now our legacy pages/organization is not functioning correctly. It is a major issue for use, and the work around I can find (making additinonal children pages under the main page to populate the report) is not sustainable or good practice.

Based on the documentation and previous releases this is a major bug that needs to be fixed.

Thanks for that feedback Mike. Unfortunately it doesn't solve my problem as I'm using the multiple page properties on the same page to be able to segregate a past state with a current state from a future state to document how the system component has changed. Therefore I can ask, "what changed for this release?" vs "how has this component changed?" vs "what changed on this project?" relative to documentation using page properties and the page properties report. I don't need different queries in JIRA and sorting to do this and JIRA anyway lacks the "why" you did the change which is more of a project kickoff deliverable. We use JIRA as well to manage our tasks during analysis, design, and implementation but when all is said and done Confluence is where we can provide an intro into what the component does and how it has changed.

Hi Guys,

You're absolutely correct about the limited functionality using the tasking and reporting feature in Confluence. Actually this is per design as Atlassian would rather have you use Jira which provides a more efficient way of managing issues or tasks. With that being said, there is integration between the two solutions that allows you to create a Jira request from Confluence. If you still insist on managing tasks in Confluence there are a couple alternative options that are close depending on your requirements. As part of the Comala Workflow plugin they have a tasking feature with reporting capabilities. While this is a slight departure it can get the job done. Here's an example.

While it's not desirable, you can put the information within a single table column.

Our team did investigate the cost to develop a customized plugin from a 3rd party source (due to limited bandwidth) and it was about 25K. Thought I would share this information with you! Take care.

Regards,
Mike

Can't agree more with the necessity to get this fixed ASAP. Thought the multiple page properties on the same page was going to be able to sort content on the page by release, project, and status so we know where a proposed change was tied to. Would love to see the same title and say this change occurred during this release and project versus this future change is during this release and this project. Is there an alternative?

Even the documentation says it's possible: https://confluence.atlassian.com/doc/page-properties-macro-184550024.html

I observe the same issue on Confluence cloud. Created a page with three individual page properties macros that each has a table with same title rows and different content. On the page with the page properties report only one of them are showing.

I also tried to add a ID to each of the page properties macros without adding the ID to the page properties report. The result is somewhat strange. If the page properties have no IDs the first page property on the page will show up in the report. If the page properties do have IDs then the last page property on the page will show up in the report.

Can we expect this to be resolved any time soon?

While creating a table with several columns and rows inside the page properties macro the page properties report marco only display's the first row.. It would be great if there was way to report on everything in the table. In our particular use case we like using the task feature for small action items but the task report is very limited. Not to mention the @ and // must be on the same line to report is a drag. Any idea on how to report against a custom table using the task feature? Looking to report on all columns and rows inside the table..

@Keith Walters definitively duplicate.

CONF-36634 also a dupe?

Any update on whether this is going to be addressed?

It looks like this has been (re-)fixed at several points in the past, so surely the correct code must be somewhere in the source repository?

Is there some sort of available work around? This functionality is exactly what we were hoping to use to solve a specific problem, but now we find it doesn't work. Are there other alternatives?

We have 5.6.3 and it does not work there either. If you put more than one page properties macros on the page, the page properties report will only collect one of them. It's quite annoying if you ask me.

I can confirm this issue in CF5.5.2

there is another fixed bug report with a possible similar cause: CONF-32367

Absolutely. Per your documentation for v5.5 here:
https://confluence.atlassian.com/display/DOC/Page+Properties+Macro#PagePropertiesMacro-UsingmultiplePagePropertiesmacrosononepage you can already do this.
This is talked about and marked as fixed here:
https://jira.atlassian.com/browse/CONF-28776
https://jira.atlassian.com/browse/CONF-32152

Basically the ID parameter was added to allow targeting only one page properties macro in a page with multiple page properties macro and if left off the report will simply report on all of them. I believe I even saw in a ticket someone complaining that there would be multiple lines for the same page because of it. I'm trying to have several of these macros on a page with no ID and using a label to report on all macros from all the pages and only one per page would show. Let me know if I just muddied it more or if you have more questions.

Hi marlon.rodriguez

Would you be able to provide details of the ticket that you are referring to here?

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian