Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-66771

Page Tree macro doesn't use the correct space when on a Column

      Issue Summary

      When we use the Page Tree macro on a column made of two columns, if one of the listed pages contains more than around 30 characters, instead of the page get listed in a line, it wraps the title in two lines, instead of one (when it has enough space to continue in just a line).

      Environment

      • Cloud

      Steps to Reproduce

      1. Have some pages on a space with the title containing more than around 30 characters;
      2. Of these pages, put some of them under another page;
      3. Insert the Page Tree macro inside a Column, starting from the 2 depth;
      4. Fill the other blank Column with random content;
      5. Get the Columns with full-width.

      Expected Results

      The listed topics from the Page Tree should be presented all in a single line while the column has enough space.

      Actual Results

      The listed pages from the Page Tree get in two-lines, even the column having enough space to continue in a single line.

      Notes

      This issue occurs eventually, not 100% of the times.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [CONFCLOUD-66771] Page Tree macro doesn't use the correct space when on a Column

            Atlassian Update - December 1, 2021

            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!

            Matthew Hunter added a comment - Atlassian Update - December 1, 2021 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!

            Amazing how many related bugs there are, and we the users have to piece them together. Here's the one I was directed to for this by support - https://jira.atlassian.com/browse/CONFCLOUD-67701.

            Just ran into this bug again today, for one more unprofessional looking page in Confluence.

            Wendy Emerman added a comment - Amazing how many related bugs there are, and we the users have to piece them together. Here's the one I was directed to for this by support - https://jira.atlassian.com/browse/CONFCLOUD-67701 . Just ran into this bug again today, for one more unprofessional looking page in Confluence.

            Gabriel added a comment -

            Should be easy enough to fix?

            Gabriel added a comment - Should be easy enough to fix?

            18 months on and still on backlog. To overcome this, I would just keep creating this in the old "new page" GUI. Now that has been removed as an option, how much longer will it take to fix a low priority fault like this? I also ask for the other 20+ faults in the new GUI that I have an interest in being fixed and equally been as long.

            Wayne Jolly added a comment - 18 months on and still on backlog. To overcome this, I would just keep creating this in the old "new page" GUI. Now that has been removed as an option, how much longer will it take to fix a low priority fault like this? I also ask for the other 20+ faults in the new GUI that I have an interest in being fixed and equally been as long.

            Tracy B added a comment -

            This should not be low priority. These ugly page trees will appear all over our converted pages! 

            Tracy B added a comment - This should not be low priority. These ugly page trees will appear all over our converted pages! 

            The following Jiras also appear to be duplicates of this one, albeit excluding the "column" requirement.

            CONFCLOUD-66884Increase/ allow custom width for Page Tree Macro in Fabric

            CONFCLOUD-54852View "Unpublished Changes" in sidebar on page tree

             

            Kevin Draggoo added a comment - The following Jiras also appear to be duplicates of this one, albeit excluding the "column" requirement. CONFCLOUD-66884 Increase/ allow custom width for Page Tree Macro in Fabric CONFCLOUD-54852 View "Unpublished Changes" in sidebar on page tree  

            LOW PRIORITY ???? Seriously??

            You break something which was working for ages and instead of fixing it you guys classify as low priority. Enough of this BS.

            Ash Srivastava added a comment - LOW PRIORITY ???? Seriously?? You break something which was working for ages and instead of fixing it you guys classify as low priority. Enough of this BS.

            Hi everyone,

            Thank you for the feedback on this bug! It looks like we have added this bug to our long-term backlog as we are focusing on some higher priority bugs and suggestions in our new editor. We will keep you updated on the progress.

            Best,

            Sunny

            Sunny Xu (Inactive) added a comment - Hi everyone, Thank you for the feedback on this bug! It looks like we have added this bug to our long-term backlog as we are focusing on some higher priority bugs and suggestions in our new editor. We will keep you updated on the progress. Best, Sunny

            Bob Sovers added a comment -

            It is apparent that Atlassian does not actually LOOK at these comments, since NO progress or update has been made here since it was created!

            Its too bad that we cannot add @Mentions to these to prompt Atlassian to respond!

             

            Bob Sovers added a comment - It is apparent that Atlassian does not actually LOOK at these comments, since NO progress or update has been made here since it was created! Its too bad that we cannot add @Mentions to these to prompt Atlassian to respond!  

            I think @Bob Sovers is right - the issue CONFCLOUD-66613 holds the wider scope on the same issue => maybe the two should be merged to fokus at only one. The "Notes" above are wrong for me: the issue appears on all pages (new editor). And yes: it looks bad.

            Martin Müller-Lindenlauf added a comment - I think @Bob Sovers is right - the issue  CONFCLOUD-66613 holds the wider scope on the same issue => maybe the two should be merged to fokus at only one. The "Notes" above are wrong for me: the issue appears on all pages (new editor). And yes: it looks bad.

              kihlberg Klaus (Inactive)
              vsiqueira Vinicius (Inactive)
              Affected customers:
              28 This affects my team
              Watchers:
              29 Start watching this issue

                Created:
                Updated:
                Resolved: