-
Bug
-
Resolution: Timed out
-
Low
-
8
-
Minor
-
1
-
Issue Summary
- When using the Page tree Macro in the new Editor, if we configure the macro with root as @self and without any search and the child page titles with the same length, when published, a new line is added.
- Macro wraps based on the longest entry, but even when the title is short (with search and no search configuration).
- Bullet point located on the top of the page tree results.
Steps to Reproduce
- Add the Page tree macro, with Search & without Search.
- Set root as @self
- Add the child pages with the same title
- Add the child pages with longer titles
Expected Results
- Page tree macro results are displayed correctly
Actual Results
- A new line when all child pages have same title length
- Macro wraps based on the longest entry, but even when the title is short (with search and no search)
Workaround
Can use Content by Label macro to list all the child pages, by adding the same label.
Also, switching the layout to wide should stop this behavior.
- duplicates
-
CONFCLOUD-65904 Allow Page Tree Macro to display items in a single line
- Closed
-
- Closed
[CONFCLOUD-68691] Page tree macro CSS problem
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: confirmed-bug ss-page-tree | New: confirmed-bug ss-page-tree stale-bulk-close202410 |
| Labels | Original: confirmed-bug | New: confirmed-bug ss-page-tree |
| UIS | Original: 2 | New: 1 |
| UIS | Original: 1 | New: 2 |
| Support reference count | Original: 7 | New: 8 |
| Description |
Original:
h3. Issue Summary
* When using the Page tree Macro in the new Editor, if we configure the macro with root as @self and without any search and the child page titles with the same length, when published, a new line is added. * Macro wraps based on the longest entry, but even when the title is short (with search and no search configuration). * Bullet point located on the top of the page tree results. h3. Steps to Reproduce * Add the Page tree macro, with Search & without Search. * Set root as @self * Add the child pages with the same title * Add the child pages with longer titles h3. Expected Results * Page tree macro results are displayed correctly h3. Actual Results * A new line when all child pages have same title length * Macro wraps based on the longest entry, but even when the title is short (with search and no search) h3. Workaround Can use Content by Label macro to list all the child pages, by adding the same label. |
New:
h3. Issue Summary
* When using the Page tree Macro in the new Editor, if we configure the macro with root as @self and without any search and the child page titles with the same length, when published, a new line is added. * Macro wraps based on the longest entry, but even when the title is short (with search and no search configuration). * Bullet point located on the top of the page tree results. h3. Steps to Reproduce * Add the Page tree macro, with Search & without Search. * Set root as @self * Add the child pages with the same title * Add the child pages with longer titles h3. Expected Results * Page tree macro results are displayed correctly h3. Actual Results * A new line when all child pages have same title length * Macro wraps based on the longest entry, but even when the title is short (with search and no search) h3. Workaround Can use Content by Label macro to list all the child pages, by adding the same label. Also, switching the layout to *wide* should stop this behavior. |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
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!