• 9
    • 13
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Would like the ability to display numbered, formatted headers. Same test style as existing headers (h1., h2., etc), but with dot-notation nested numbering.

      Maybe something like: h#., h##., h###., etc.

      So markup like:
      h#. One
      h##. One-one
      h##. One-two
      h#. Two
      h##. Two-one
      h###. Two-one-one

      would display as if markup was entered:

      1. One

      1.1 One-one

      1.2 One-two

      2. Two

      2.1 Two-one

      2.1.1 Two-one-one

      Notice that the heading levels start at h2 since h1 is really too big for this usage.

      Atlassian Status as of January 2019

      Hi All,

      Thank you for your feedback on this issue thus far. We acknowledge that many teams require numbered headings for many cases ranging from specifications to the legal profession.
      At present, this issue is not on our short term roadmap.
      Please consider one of the many add-ons in the marketplace which provide this functionality:

      Cloud and Server

      Server only

      Many users have indicated that they need flexibility in the way this feature should work for them. Please do comment to let us and our add-on vendors know if these add-ons do not provide the functionality which you need.

      Confluence Product Management

        1. nestedcss.txt
          3 kB
        2. nestedcss-update.txt
          3 kB
        3. screenshot-1.jpg
          screenshot-1.jpg
          16 kB

            [CONFSERVER-1732] Numbered Headings

            Enrico Stahn added a comment - - edited

            This is ridiculous. 66c per user for a plugin that should be standard. You guys should get rid of Bold/Italic/etc so this can be implemented as separate plugins too.

            Enrico Stahn added a comment - - edited This is ridiculous. 66c per user for a plugin that should be standard. You guys should get rid of Bold/Italic/etc so this can be implemented as separate plugins too.

            Seriously Atlassian??? First you force us to use the f** cloud version and then you dont even provide the BASIC functinality of a standard Editor????

            Why should be pay for this!? In the server version we hat the CSS functionality to do this stuff. Just implement the basic functions of the server version.

            With our company (1000+ users) we tend o NOT move to the cloud version of confluence and rather change the tools.

            Benjamin Löffler added a comment - Seriously Atlassian??? First you force us to use the f** cloud version and then you dont even provide the BASIC functinality of a standard Editor???? Why should be pay for this!? In the server version we hat the CSS functionality to do this stuff. Just implement the basic functions of the server version. With our company (1000+ users) we tend o NOT move to the cloud version of confluence and rather change the tools.

            Hi here,

            We have https://marketplace.atlassian.com/apps/16063/numbered-headings?tab=overview&hosting=cloud which offers both P2 & Cloud.  FYI. 

            Thanks

            Rama Krishna Anumola {Appfire} added a comment - Hi here, We have https://marketplace.atlassian.com/apps/16063/numbered-headings?tab=overview&hosting=cloud which offers both P2 & Cloud.  FYI.  Thanks

            This likely isn't ever going to be fixed by Atlassian – I've found a good alternative for our internal blogs, specs, and other docs: readthedocs. Markdown and Sphinx are both much more pleasant to deal with than the WSYWIG thing in Confluence (which is still broken years later) and its easy to get numbered headings (and many other documentation oriented features). You can put your docs tree in git so its easy to see and manage changes (something that's pretty hard with Confluence). The biggest pain is if you want to insert images or drawings you have to put the file in your docs tree and write a link in the markdown (you can't just drag the image into the doc).

            If you want to host it locally its pretty easy to stand up your own version of readthedocs or just use 'mkdocs' directly in a git tree.

            Eric Varsanyi added a comment - This likely isn't ever going to be fixed by Atlassian – I've found a good alternative for our internal blogs, specs, and other docs: readthedocs. Markdown and Sphinx are both much more pleasant to deal with than the WSYWIG thing in Confluence (which is still broken years later) and its easy to get numbered headings (and many other documentation oriented features). You can put your docs tree in git so its easy to see and manage changes (something that's pretty hard with Confluence). The biggest pain is if you want to insert images or drawings you have to put the file in your docs tree and write a link in the markdown (you can't just drag the image into the doc). If you want to host it locally its pretty easy to stand up your own version of readthedocs or just use 'mkdocs' directly in a git tree.

            Needs to be in the standard version of Confluence.

            Stefan Huber added a comment - Needs to be in the standard version of Confluence.

            Same, if Atlassian asks me to pay up to get numbered headings... for god's sake, I can't move more employees onto such system

            Bart Van Pee added a comment - Same, if Atlassian asks me to pay up to get numbered headings... for god's sake, I can't move more employees onto such system

            Will added a comment -

            Atlassian no longer seeks to improve its software when it can make money off of other people doing it, ie plugins.  We are looking to slowly replace our Atlassian software.

            Will added a comment - Atlassian no longer seeks to improve its software when it can make money off of other people doing it, ie plugins.  We are looking to slowly replace our Atlassian software.

            I do also join the opinion of my pre-commenters: such a simple feature should definately not be an add-on but part of a standard version - included in the tool-bar!

            Stephanie Helmeth added a comment - I do also join the opinion of my pre-commenters: such a simple feature should definately not be an add-on but part of a standard version - included in the tool-bar!

            evsmirnov added a comment -

            Bump - something simple as "Number all headings on the page" would be great. Same numbers as in the Table of Contents macro. Numbers are very helpful when you have to refer to page content during discussion.

            evsmirnov added a comment - Bump - something simple as "Number all headings on the page" would be great. Same numbers as in the Table of Contents macro. Numbers are very helpful when you have to refer to page content during discussion.

            Bump - this needs to be in the standard version of Confluence.

            Emma Lundin added a comment - Bump - this needs to be in the standard version of Confluence.

              Unassigned Unassigned
              e50271f7cd6d Dan Nathanson
              Votes:
              611 Vote for this issue
              Watchers:
              286 Start watching this issue

                Created:
                Updated: