-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
5.9.1, 5.8.16, 5.8.17, 5.9.4, 6.0.0-OD-2016.06.1, 5.10.3, 5.10.5, 6.5.1
-
7
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
When using the Page Properties Report macro will not show results if used with a Page Properties macro that has a Page Properties ID that begins with zero (0)
Steps to Reproduce
- Create a page in Confluence and add the Page Properties macro
- Add a table (at least 2 columns) inside the macro (remove the header row and add data in each section of the table)
- Edit the Page Properties macro to add a Page properties ID that begins with ‘0’ (ex. 007)
- Add a label to the page and save the page
- Create another page and add the Page Properties Report macro
- Enter the label from the previous page in the Label section
- Expand the Options section and enter the Page properties ID from the other page that begins with ‘0’
- Save the page
Expected Results
We would expect that the information from the page properties macro would generate in the page properties report macro. We can even see the correct information in the preview of the Page Properties Report Macro, but it does not render once saved.
Actual Results
No information renders and a message 'No Content Found' is displayed
Notes
This issue appears to have began in version 5.8.16. This was working in Confluence 5.8.5 and 5.8.15. This is not working in 5.8.16, 5.8.17,5.9.1,5.9.4,6.5.1
- is incorporated by
-
CONFSERVER-42801 Umbrella Issue for Page Property and Page Properties Report Macro
-
- Closed
-
- relates to
-
CONFCLOUD-40740 The Page Properties Report macro shows no results if corresponding page properties ID begins with '0'
-
- Closed
-
[CONFSERVER-40740] The Page Properties Report macro shows no results if corresponding page properties ID begins with '0'
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-cloud affects-server macros page-properties page-properties-macro page-properties-report-macro | New: affects-cloud affects-server cleanup-seos-fy25 macros page-properties page-properties-macro page-properties-report-macro |
UIS | Original: 2 | New: 0 |
UIS | New: 2 |
Support reference count | Original: 6 | New: 7 |
Support reference count | Original: 7 | New: 6 |
Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
Support reference count | Original: 6 | New: 7 |
Workflow | Original: JAC Bug Workflow v3 [ 2902233 ] | New: CONFSERVER Bug Workflow v4 [ 2996828 ] |
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