Configuring a specific column, from migrated pages, in Page Properties Report Macro results in missing values

Issue Summary

The users are encountering issues with the Page Properties Report Macro in both legacy and new editors, after migrating to the cloud.

The issue resides in how some tables are structured in OnPrem vs Cloud.

• This is reproducible on Data Center: No

Steps to Reproduce

In Legacy Editor:

1. Access a page with the Page Properties Report Macro. A specified column, for example, 'Number' does not appear unless directly configured in the Macro Settings.
2. When the 'Number' column is explicitly included (Columns to display), the values are not shown in the report.

In the New Editor:

1. Access a page with the Page Properties Report Macro. The column works as expected, but the values are never shown.

Screenshot:

Expected Results

In both editors, the selected column should display as expected and their values should be shown in the report.

Actual Results

The 'Number' column and its values are not displayed correctly in the report and the issue persists even after configuring in the Macro Settings. 

Workaround

Currently, there are two workarounds for this behavior:

1. Convert the affected pages to the new editor. This action will fix the issue as the tables will be converted to a supported format.
2. Fix the legacy pages by recreating the tables, either manually or by utilizing regular expressions (Regex) using the API to update the pages.

Notes

This issue appears to be related to the storage format from the migrated pages with the 'Page Properties' Macro.

• The table format being used is in an unsupported manner, consider what is required in order to be "read" by the Page Properties Report macro in Confluence Cloud, while the following pattern is somehow acceptable while in Confluence OnPrem:

<thead><tr><th style="text-align: left;">Number</th><td style="text-align: left;">2132</td></tr></thead><colgroup><col /><col /></colgroup>

The page working has the below Storage Format:

<p class="auto-cursor-target"><br /></p><ac:structured-macro ac:name="details" ac:schema-version="1" ac:macro-id="798133ba-0e4d-4a5b-9609-0741f41efdda"><ac:parameter ac:name="id">456</ac:parameter><ac:rich-text-body>
<p class="auto-cursor-target"><br /></p>
<table><colgroup><col /><col /></colgroup>
<tbody>
<tr>
<th>Number</th>
<td>12345</td></tr>
<tr>
<th>Type</th>
<td>ERROR</td></tr>
<tr>
<th>Origin</th>
<td><span class="legacy-color-text-blue3">Error Origin</span></td></tr></tbody></table>
<p class="auto-cursor-target"><br /></p></ac:rich-text-body></ac:structured-macro>
<p class="auto-cursor-target"><br /></p>

A broken page (migrated one) has this another one:

<p class="auto-cursor-target"><br /></p><ac:structured-macro ac:name="details" ac:schema-version="1" ac:macro-id="8bcd7ea8-b05a-4061-9352-ce0b876706fa"><ac:parameter ac:name="id">321</ac:parameter><ac:rich-text-body>
<p class="auto-cursor-target"><br /></p>
<table>
<thead>
<tr>
<th>Number</th>
<td>654321</td></tr></thead><colgroup><col /><col /></colgroup>
<tbody>
<tr>
<th>Type</th>
<td>TEST</td></tr>
<tr>
<th>Origin</th>
<td>Another Origin</td></tr></tbody></table>
<p class="auto-cursor-target"><br /></p></ac:rich-text-body></ac:structured-macro>
<p class="auto-cursor-target"><br /></p>