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

Table of Contents macro is not working with the excerpt and excerpt include macros

    • 17
    • 8
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      PM's response

      Hi everyone,

      I’m Tiffany and I’m a product manager on the Confluence team. We would like to thank you for your comments about the way the Table of Contents macro works within the Excerpt and Excerpt Include macros.

      We designed the Table of Contents macro to only work within the page, blog or macro it has been inserted. It cannot reference or be referenced across multiple pages or blogs, meaning that when it is added to an Excerpt macro, it will only display headings located inside the excerpt. Those heading links won't navigate to the source page.

      Based on that, the functionality reported for Table of Contents Macro is actually not a bug, it is working as expected, which we also updated the documentation to reflect it:

      https://support.atlassian.com/confluence-cloud/docs/insert-the-table-of-contents-macro/

      I have thus made note of this expected behavior in the Table of Contents documentation and converted this bug to a feature request so that you can track our progress.

      Best,
      Tiffany

      Issue Summary

      If you add a Table of Contents inside an Excerpt macro, the TOC won't load on the page. If you add the Excerpt include macro on another page to display this TOC, it won't display in there as well. 

      Steps to Reproduce

      1. Create a page (Page A).
      2. Add headings to it.
      3. Add an Excerpt macro.
      4. Place a TOC macro inside the Excerpt macro.
      5. Publish the page.
      6. Create a new page (Page B).
      7. Add an Excerpt Include macro, configured to display the Excerpt created on Page A.

      Expected Results

      Since the Excerpt is not configured to hide the content, the TOC should load on both pages:

      • Page A.
      • Page B.

      Actual Results

      The macro doesn't load on any of the pages.

      Workaround

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

            [CONFCLOUD-72469] Table of Contents macro is not working with the excerpt and excerpt include macros

            This feature is really appreciated. Please, fix.

            Kristian Belov added a comment - This feature is really appreciated. Please, fix.

            Yep, 18ff56543dcf   - you pass with flying colours.

            Allow me to summarise your summary:

            Atlassian f*cked its customers and doesn't give a sh*t. It did this years ago and has demonstrated for years it still doesn't give a sh*t.

            As with johnlockhart's reply to you, this is my personal opinion and does not represent that of my employer or any other entity, human, corporate or otherwise.

            It takes a lot for me to be so publicly crass - take that as a measure of the frustration that Atlassian's decisions have induced. I'm still incredulous that no competitor has recreated the missing functionality. I'd move all my docs over in a heartbeat.

            youcantryreachingmeN added a comment - Yep, 18ff56543dcf   - you pass with flying colours. Allow me to summarise your summary: Atlassian f*cked its customers and doesn't give a sh*t. It did this years ago and has demonstrated for years it still doesn't give a sh*t. As with johnlockhart's reply to you, this is my personal opinion and does not represent that of my employer or any other entity, human, corporate or otherwise. It takes a lot for me to be so publicly crass - take that as a measure of the frustration that Atlassian's decisions have induced. I'm still incredulous that no competitor has recreated the missing functionality. I'd move all my docs over in a heartbeat.

            johnlockhart added a comment - - edited

            Well said 18ff56543dcf I concur. This sort of spin and disinformation is certainly making me look for any viable alternative. disclaimer: this is my personal opinion and does not represent that of my employer or any other entity, human, corporate or otherwise.

            johnlockhart added a comment - - edited Well said 18ff56543dcf I concur. This sort of spin and disinformation is certainly making me look for any viable alternative. disclaimer: this is my personal opinion and does not represent that of my employer or any other entity, human, corporate or otherwise.

            OK, let me summarize the information I got here and by my analysis:
            TOC was working with excerpt macro in Data Center, as I understood also in the old editor in cloud.
            All users were happy with that, but Atlassian product management thought it would be a good idea to remove this functionality with the new editor.
            Or was there a feature request with tons of votes existing to remove that?! I can't believe there is one existing as I can't imagine there is any useful use case why I need to show only a part of headers with TOC. If I don't want to show a header, I'll not define it as a header, doesn't matter where it comes from - finished.
            Moreover you don't call it bug, because it works like it was defined. So it's a feature request now, waiting for years and thousands of votes, before you'll take care of it to bring back a feature, nobody asked you to remove it?

            Summarized that means you invest time to change things no customer asked for and let customers wait years not even for new features, just to bring back what they already had? Seems the product management has the right focus on the user who finally works with the software... sarcasm-off

            Bernhard G. added a comment - OK, let me summarize the information I got here and by my analysis: TOC was working with excerpt macro in Data Center, as I understood also in the old editor in cloud. All users were happy with that, but Atlassian product management thought it would be a good idea to remove this functionality with the new editor. Or was there a feature request with tons of votes existing to remove that?! I can't believe there is one existing as I can't imagine there is any useful use case why I need to show only a part of headers with TOC. If I don't want to show a header, I'll not define it as a header, doesn't matter where it comes from - finished. Moreover you don't call it bug, because it works like it was defined. So it's a feature request now, waiting for years and thousands of votes, before you'll take care of it to bring back a feature, nobody asked you to remove it? Summarized that means you invest time to change things no customer asked for and let customers wait years not even for new features, just to bring back what they already had? Seems the product management has the right focus on the user who finally works with the software... sarcasm-off

            Hi all,

            I ran into this myself, so I've added this as a feature to my macro Floating Table of Contents for Confluence so that any headings from both Include Page macro contents and Excerpt contents are also displayed in the Table of Contents on the parent page and are fully clickable. At the moment this is only available as a Floating Table of Contents on the side but if enough people are interested, I can make a standard "sits at the top" style Table of Contents macro with this feature,

            thanks, Matt

            Matthew Grover added a comment - Hi all, I ran into this myself, so I've added this as a feature to my macro Floating Table of Contents for Confluence so that any headings from both Include Page macro contents and Excerpt contents are also displayed in the Table of Contents on the parent page and are fully clickable. At the moment this is only available as a Floating Table of Contents on the side but if enough people are interested, I can make a standard "sits at the top" style Table of Contents macro with this feature, thanks, Matt

            Seriously, this is the exact reason for excerpts. This is clearly a defect by the exact definition.

             

            The most basic of basic table of contents for an entire document root would require the table of contents from all it's subpages.

             

            And confuence's sole mission is to be a documentation source.

            Brandon Tamm added a comment - Seriously, this is the exact reason for excerpts. This is clearly a defect by the exact definition.   The most basic of basic table of contents for an entire document root would require the table of contents from all it's subpages.   And confuence's sole mission is to be a documentation source.

            I just recently found out about this issue after my company moved to cloud version of Confluence. It's very disappointing.

            Tomasz Kowalczewski added a comment - I just recently found out about this issue after my company moved to cloud version of Confluence. It's very disappointing.

            Kassandra 'Kasey' Karan added a comment - - edited

            Why is confluence removing functionality used by hundreds of users? You can look at the vote count on this story to confirm this number. This smells like product owners not wanting to support creative use cases outside of the narrow use case that you defined. You need to adjust your product vision and support policy if you think this is acceptable. 
            If your editor didn't break when you have a large document or if you hadn't removed your MSWord import page by heading feature (aaaaaaaaaa) this wouldn't be as annoying.

            Kassandra 'Kasey' Karan added a comment - - edited Why is confluence removing functionality used by hundreds of users? You can look at the vote count on this story to confirm this number. This smells like product owners not wanting to support creative use cases outside of the narrow use case that you defined. You need to adjust your product vision and support policy if you think this is acceptable.  If your editor didn't break when you have a large document or if you hadn't removed your MSWord import page by heading feature (aaaaaaaaaa) this wouldn't be as annoying.

            As this function was working in Confluence on server I am wondering why this basic feature is not also working on cloud.

            tomas.kadlec added a comment - As this function was working in Confluence on server I am wondering why this basic feature is not also working on cloud.

            Good to know this BUG still isn't fixed, thanks for the very useful feature Atlassian.

            Darren Nicas added a comment - Good to know this BUG still isn't fixed, thanks for the very useful feature Atlassian.

              smalkireddy@atlassian.com Siddharth Reddy Malkireddy
              edc026a7b429 Vitor A (Inactive)
              Votes:
              210 Vote for this issue
              Watchers:
              118 Start watching this issue

                Created:
                Updated: