-
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
My company is experiencing this issue as well. An updated status would be appreciated.
Ashley Bowman
added a comment - Circling back for an update. I agree with Kevin, please inform us if this will be moved into the Atlassian Backlog or addressed in some manner.
Ashley
Ashley Bowman
added a comment - Circling back for an update. I agree with Kevin, please inform us if this will be moved into the Atlassian Backlog or addressed in some manner.
Ashley Hi Team,
I understand that you have a process to follow, I'm totally comfortable with that, but I would really like to see any kind of statement about whether this will be triaged into the active backlog or if it is going to die here on the vine. Can you please let us know what your thoughts are on whether this can/will be worked on? That would tell us how urgently we need to explore alternatives.
Cheers!
Ashley Bowman
added a comment - Hi, is there an update on this issue? It continues to negatively impact our instance. We would like an update as soon as possible on whether a fix is being actively worked on, and whether Atlassian is taking an aggressive stance against this. This bug was added due to the upgrade of our Confluence environment to 5.9.7; it broke existing functionality, and should therefore be prioritized against other requests.
Ashley Bowman
added a comment - Hi, is there an update on this issue? It continues to negatively impact our instance. We would like an update as soon as possible on whether a fix is being actively worked on, and whether Atlassian is taking an aggressive stance against this. This bug was added due to the upgrade of our Confluence environment to 5.9.7; it broke existing functionality, and should therefore be prioritized against other requests. Hey Team, Can we get a meaningful update as to whether this is going into development and/or when that will happen? Our client has 100's of instances in Confluence where this is broken. We simply can't use the work around in an effective fashion.
On behalf of customer from CSP-172994:
Note that this is having a negative impact on our Atlassian instance. The Page Properties Gadget is heavily used heavily throughout all spaces, and many of the pages that are pulled in use formatting macros that are "owned" by Atlassian, such as the Expand gadget.
Clearing formatting from each page is simply not an option, due to the popularity of the gadget and macros, as well as the bulk of pages involved (over 500+). This is not a viable workaround for our implementation.
Seeing as the upgrade to Confluence 5.9.7 caused a break in existing functionality, we believe Atlassian should take a more aggressive stance to resolve this.
Please let us know if we have any updates on it.
I want to make sure that this ticket takes into account the Expand Gadget, which (when used on a page) also breaks the Page Properties Report gadget in a similar way, when that gadget references a page with the Expand Gadget on it.
Going back to all of our hundreds of pages and searching for Expand gadgets to try to implement a workaround is not a feasible fix... this bug needs to be addressed, please.
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