-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
5.6.6, 5.8.10
-
6
-
Severity 3 - Minor
-
0
-
Steps to reproduce:
- create a few pages and insert Page Properties Macro
- in the Page Properties Macro, use formatting. Eg: as screenshot InsertMarkup.png attached:
|Title| bababa| |{{Metadata1}}|dummy 7| |{{Metadata2}}|dummy 8| - label the page . Eg: rambutan
- in the Page Properties Macro, use formatting. Eg: as screenshot InsertMarkup.png attached:
- create a page, insert the Page Properties Report Macro
- use the label created in step 2.2
- Access the page that contain Page Properties Report
- Page 1 will shows all column correctly
- click on Next, (BUG) some of the columns has empty rows
- go back to Page 1, (BUG) some of the columns also empty
- refresh the Page 1, the columns will be showing the correct data
Workaround
Clear the Page Properties Macro's format and it will fix the problem as shown:
- is incorporated by
-
-
- Closed
-
[CONFSERVER-39345] Page Properties Report Shows Empty Column When Formatting Is Used
| QA Demo Status | New: Not Needed [ 14332 ] | |
| QA Kickoff Status | New: Not Needed [ 14236 ] | |
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server page-properties-report-macro | New: affects-server cleanup-seos-fy25 page-properties-report-macro |
| UIS | Original: 2 | New: 0 |
| UIS | Original: 0 | New: 2 |
| UIS | Original: 1 | New: 0 |
| Support reference count | Original: 5 | New: 6 |
| Support reference count | Original: 6 | New: 5 |
| Component/s | New: Macros - Page Properties [ 40391 ] | |
| Component/s | Original: Editor - Page / Comment Editor [ 40706 ] |
| Labels | Original: affects-server editor page-properties-report-macro | New: affects-server page-properties-report-macro |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center