-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Major
-
Issue Summary
Page property report macro not showing correct report when child pages are moved in page tree.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create two pages called them Parent 1 and Parent 2 respectively.
- Now create child page under Parent 1 call it Child page 1.
- Create two sub-child pages with Child page 1 call them SP1 and SP2
- Add two report macros in Parent1 one for Parent 1 and other Parent 2 with filter Ancestor
- Add page property macro in SP1 and SP2
- It will show right results with in Parent 1 where report macro is added.
- Now move the SP1 under Parent 2.
- It will show right results again with each property report added in Parent 1.
- Move Child page 1 along with SP2 under Parent 2.
Expected Results
It should show all the results under where ancestor is selected as Parent 2
Actual Results
Its showing page property results one in Parent1 and other in Parent 2. However all the pages are moved under Parent 2 already.
Workaround
Running a reindexing fixes the issue. However Organisation where re-org and reparent of pages are happening running reindex and user reaching out to support multiple times is not feasible.
[CONFCLOUD-74295] Page property report macro issue when pages are moved in page tree.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Hi 505da7f6a08d ** I’ve updated this bug to reflect that is a confirmed bug based on your additional information. Thank you for your patience as the Confluence team works on investigating this further.
Best,
Oksana
Hi everyone,
This is Oksana from the Confluence team. Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review.
Thank you again for providing valuable feedback to our team!
Best,
Oksana
Hi Trupti Das and everyone,
This is Oksana from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the described behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?
We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.
Best,
Oksana
bandicam 2022-11-15 09-07-41-633.mp4
mhunter
Yes, this bug is still impacting the team.