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.

Hi here,

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

Thanks

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

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!

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.

I agree - it is very strange such a simple thing a lot of users explicitly ask for has not been implemented for one and a half decade.

In my opinion, "buy the add-on" is not a resolution.  A workaround?  Yes.  But NOT a resolution of an issue.  Just curious, does anyone have a sense of just how much effort it would really require for them to program this into the baseline product (as is already present in Confluence and as many marketplace providers have done)?

There must be some financial (or other) incentive for this to not make it on the short list of low-hanging fruit after 14 years of being discussed.

I can only join the preview commenters to stress this is really a must have feature.

I can only agree with Hugo Tavares: this is a basic functionality, any tool of that kind should have.

OT: I recently found this issue (https://ecosystem.atlassian.net/browse/STRM-12) being completely abandoned by Atlassian for 2.5 years. Last comment by the devs: "We're currently working on this issue and will have it released soon hopefully." How can this even happen?

This is just a sad commentary on Atlassian.

Hi,

Actually, and from my experience of 5+ years using this tool, I find it quite a displeasing position from Confluence's POs to postpone this feature (again!) one more year, since currently it is costly to integrate the available options on Atlassian's Marketplace.
It will be one more year that, for instance, my company, my team and myself, will have to workaround by manually typing the numbered headings and therefore possibly baffling technical docs OR, worst case scenario, having collaborators adhocly using hacks that can ultimately break up Confluence's functionally (such as the ones referred here: Is it possible to add numbering to headings in Confluence?).

Plus, for a collaborative documentation tool, as it was mentioned many times along this thread, this SHOULD BE an out-of-the-box feature of Confluence, thus this is not a "Nice to have" but a "must have".

I honestly hope you revise this.

Thank you.

Thanks for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

13 years and it's "not on our short term roadmap"... Makes me wonder how long their long term roadmap is...

Instead of wasting time reinventing existing default user environment functionality, why not cover the basics first?

@Jonas Marek Check out Easy Numbered Headings if you don't want to have to use a macro to get numbering for your headings.

@Jan-Peter Rusch, thanks for the recommendation! Your suggestions have been implemented, and more are welcome.

There's some movement on this issue & a new (free) addon seems promising.

I gave Easy Numbered Headings a try.

While it doesn't fulfill all our requirements by now, support & marketing is very active & seems to be eager to take use cases provided by customers into account. I suggested a "Switch Off" macro for space where this addon is active and an option to configure a number prefix by a macro inside a page so that a documentation which consists of many page can have a page prefix offsetting the "normal" numbering.

I've had success working around this by placing a CSS script inside HTML macro to the page, taking inspiration from http://philarcher.org/diary/2013/headingnumbers/. This will support numerical numbering up to 6 level deep:

<style>
  div.wiki-content {counter-reset: h1}
  div.wiki-content h1 {counter-reset: h2}
  div.wiki-content h2 {counter-reset: h3}
  div.wiki-content h3 {counter-reset: h4}
  div.wiki-content h4 {counter-reset: h5}
  div.wiki-content h5 {counter-reset: h6}

  div.wiki-content h1:before {counter-increment: h1; content: counter(h1) ". "}
  div.wiki-content h2:before {counter-increment: h2; content: counter(h1) "." counter(h2) ". "}
  div.wiki-content h3:before {counter-increment: h3; content: counter(h1) "." counter(h2) "." counter(h3) ". "}
  div.wiki-content h4:before {counter-increment: h4; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) ". "}
  div.wiki-content h5:before {counter-increment: h5; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) ". "}
  div.wiki-content h6:before {counter-increment: h6; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) "." counter(h6) ". "}
</style>

The linked addon linked as a Workaround is not really helpful since you have to use the macro all the time when writing text.

Will there be a solution of Atlassian soon? At least some update of the roadmap would help.

Can Atlassian please provide an update on this issue? It seems there are enough interested to support it. I'd be happy with a supported macro that doesn't require style sheet changes.
I just tested what happens with numbers and indents and bullet points in Confluence. It doesn't work. The numbers get out of whack. The result is shown below. (2 x b's and Heading Two is numbered as 3.)
1. Heading One.
a. Point one.
b. Point two.

• Bullet point to point two.
  b. Point three.
  3. Heading Two.

In terms of technical documentation, its a bit tricky. It makes sense that the web provides a clean interface to be accessed across devices. You don't exactly want to be trawling through a manual on your phone. But you still want that ability especially when you're shipping documentation.
For us the best compromise seems to have been to export the space with standard word document templates configured with numbered headings:
https://support.office.com/en-ca/article/Number-your-headings-ce24e028-4cb4-4d4a-bf25-fb2c61fc6585
and the scroll office plugin to pipe it through:
https://marketplace.atlassian.com/plugins/com.k15t.scroll.scroll-office
Which deals very well with generating professional documentation, we don't manually change anything from there its automatically exported by our continuous integration build server and put in the release.
Then for the web view we use the engineering essentials plugin to number all the headings in the space:
https://marketplace.atlassian.com/plugins/com.precisionplugins.engineeringessentials
It's numbered per page, but if you're looking on your device you don't want to see a whole hierarchy of numbers, that's what the tree view / navigator is for, you're really only interested in the current context, which is why the different web presentation makes sense.

So far people seem happy, but I guess they're not aware of the background work that was involved in getting it all running smoothly.

Peter and Ronald are right on the money. I also stopped advocating Confluence years ago (when wiki was ripped out).
Atlassian is unique, in my experience, for abusing customers in these ways.
The FedEx days, imo, is perhaps a symptom of the problem, not a path to resolution. Who decides what gets done on a FedEx day? Us, the users and external advocates? No. It is for them to jazz themselves up internally.

We all suffer from the same thing: We thought we were entering into a collaborative relationship w Atlassian, and found ourselves in, what amounts to, an abusive one.

To me this is yet another example of modern day product management gone awry in the worst way. Unfortunately various Atlassian product managers over time have exhibited the same behavior so one may assume its part of the guidelines.
Those of us who've seen this same behavior on other requests over the past YEARS all know the classic answers we've gotten to various reported issues, but what it comes down to is that Atlassian development, guided by product management one assumes, and evidentially without scrutiny from the founders (who in their beginning growth of the company were responding to these issues with much more resolution than when they handed this off to a product management function).
I think its time for Mike and Scott to examine the backlog of issues (even the multitude of conveniently closed (by the product managers over time) ones and re-examine what makes a lot of sense and opening those up again for resolution. They should spend some of the famous FexEd time on this for a change. In addition, I think it is time to examine the classic rules the product managers employ, as other posters have said, those of us who were your self selected champions in the days have great trouble continuing to explain to our companies why Atlassian is so unresponsive to fixing some core functionality. As it stands, I am not advocating Confluence anymore for its original purposes we once wanted it to be a complete solution for. We're looking at other solutions now, and closely scrutinizing the various contenders contractual language about commitments to their customers and their core functionality.
Re-install our trust and commitment to Atlassian, and through us, our "customers", be they internal or external. Mike, Scott, the ball is in your court.

I don't think this feature is only (or primarily) for old fashioned outliners, it is for technical documentation and manuals. Since Atlassian's products are first and foremost for technical companies transitioning from out-dated documentation methods, I'm really confused why this wasn't one of the first features of Confluence. We like to export to PDF for our customers. So when I need to refer to specific points for our customers, I need to just say "well, just do a search for <insert heading name>" rather than just giving them a sub-section number as you would for typical manuals. Which is rather unprofessional. I've started to go back to Word. So now I need to export to Word, do a whole bunch of touch up to add numbered headings, and then hope that things on the wiki and word document don't get too out of sync because its a painful process. I just want to write software, not mess with Word formatting all day.

I will say that with the per site-space PDF export CSS formatting and other super advanced features on Confluence, you can actually make a pretty good looking technical manual directly.... just needs numbering!

I was idly wondering whether Confluence would become a real wiki again (e.g. bring back proper wiki markup editor).

Atlassian had to tell me 50 times that the wiki is dead.

The same goes, it seems, for numbered headings. (Only old fashioned outliners need those...)

I was idly wondering whether Confluence might perhaps support numbered headings, and upon finding this thread, am utterly gobsmacked that what I consider to be a basic MVP feature is missing. Not only that, but requested eleven years ago, and still not implemented. If the company I work for had been that negligent of our own customers, we would have gone out business a decade ago or more.

I realise that Atlassian positions itself as the cheap-as-chips alternative to other more elegant products out there in various spheres, but come on, we are a paying customer, and this is in the top 5 list of feature enhancements.

Just do it

I'm pretty sure this ticket has become an internal joke or meme within Atlassian.

This would be a very useful feature. Hoping there is some movement on it soon.

I would pay USD 5 to get Atlassian to finally say "Confluence is no longer a wiki" and USD5000 to get wiki markup back as a native feature.

I would pay USD 5 to get a response on this thread from Atlassian's VP of Product.

This prob has no chance because it is wiki-like, and confluence is no longer a wiki....
(tear rolling down cheek)

Wow, this is the #5 top-voted open confluence issue. And its been open for over 10 years. Not a good sign!

Be careful what you ask for the "headings" feature might be dropped like the old cal plugin and be brought back as a payed addon with loads of features

Any update on this?

1. It's SO BASIC.
2. It's been around for 10 YEARS as a feature request.
3. Please add it.
4. Err...
5. That's it.

We really shouldn't have to pay for 3rd party add-ons for this kind of stuff.

This is such a basic editing feature. I agree with Jim above. It is astonishing that something as basic as this requires a paid third party plugin. What is the thinking here?

Could also be achieved by editing the global or space CSS; e.g.:

#com-atlassian-confluence .wiki-content h1:before {    
    content: counter(Level01) ". ";    
    counter-increment: Level01;    
}    
#com-atlassian-confluence .wiki-content h1 {    
    counter-reset: Level02;  
}  
#com-atlassian-confluence .wiki-content h2:before {  
    content: counter(Level01) "." counter(Level02) ". ";  
    counter-increment: Level02;  
}  
#com-atlassian-confluence .wiki-content h2 {  
    counter-reset: Level03;  
}  
#com-atlassian-confluence .wiki-content h3:before {  
    content: counter(Level01) "." counter(Level02) "." counter(Level03) ". ";  
    counter-increment: Level03;  
} 

Sigh... I wish Atlassian just incorporated the improvements that you guys make into their product...

Engineering Essentials has just been released to the public. https://marketplace.atlassian.com/plugins/com.precisionplugins.engineeringessentials

This resolves the issue of numbered headings space-wide, without needing to put your content inside a macro.

With Engineering Essentials it is now possible to configure an entire space to have numbered headings. Any enabled space will instantly have it's headings numbered. No additional editing of a page is required. This enforces a consistent look and feel within each space. Additionally, because your content does not need to be wrapped in a macro it does not interfere with page differences, change emails, exports, or other plugins. Ensuring your content will continue to be available into the future, regardless of what plugins you have installed. This simplifies export templates and improves compatibility by defining the correct layout for the particular format within your own templates.

As numbered headings are often required for formal documentation we've also provided the ability to separately force version comments on all changes within a space. Enabling fully automatic change history documentation.

With years of experience supporting Confluence in an engineering environment, Precision Plugins have big plans to plug some small gaps, helping Confluence and other extensions be the best environment for your formal documentation.

Checkout the Engineering Essentials package and let us know what you think here:
https://marketplace.atlassian.com/plugins/com.precisionplugins.engineeringessentials

I've only recently come to Confluence, to find this issue has been unresolved for 10 years is unbelievably disappointing. As the company I have started with have Confluence in place I would have liked to work to make it useable for them, I'll be keeping my eye out for another wiki/doc management program as my needs are rapidly overwhelming the functional ability of Confluence.

@Gert-Jan van de Streek You are right about the WYSIWYG, sorry for the confusion, I changed my previous comment accordingly. What I basically meant was that there should be no need to embed the whole page into the NH macro body. (Like in https://bitbucket.org/avisi/numbered-headings/issue/3/make-macro-without-body)

@Stephan Vollmer Are you on OnDemand with numbered headings? I am asking because Numbered Headings is fully WYSIWYG, we put a lot of effort in that for the download version (which is still free). On OnDemand the restrictions on the plugin architecture there prohibit us from injecting the nessecary JavaScript to do so, so for the OnDemand version, indeed no WYSIWYG there.

Another thing, reading the above we are considering investigating on something that has been brought up a few times before, turning on numbered headings for a whole page, or even space. Not sure how easy it is but if there is enough interest, we might feel up to the task. Please file an issue or add ideas, or vote on https://bitbucket.org/avisi/numbered-headings/issue/33/one-switch-to-enable-numbering-for-a-space.

https://confluence.atlassian.com/display/DOC/Confluence+4+Editor+-+Customer+Feedback?replyToComment=433391782&#comment-433391782

Do not blame you. We had abandoned Confluence for the same reason. My take is that Atlassian does not have the technical talent and the company leadership to address this.

As a stock investor, I would have severe reservations about investing in a company that does not understand the ramifications of having a problem go unresolved for 10 years.

Sadly, I will be bowing out of this thread and our use of Confluence. Our company's requirements for technical documentation require such a feature, so, we will have to pass Confluence. Hopefully Atlassian surprises this issue and all of you with a resolution soon, before its 10 year anniversary! Good luck to you all!

It is hard to believe so many people use Confluence without such an important feature being an integral part of Confluence!
I wonder what the Confluence designers were thinking when they decided to not include this feature.

Cannot understand either that such an essential feature for technical documentation is still missing.

Yes, the Numbered Headings plugin is great and I appreciate the work, but this functionality should be bundled and supported. The problem with the NH plugin is that the whole page needs to be nested into one macro body which can be quite distracting for long pages.

Wow, an issue that has been open for almost 10 years! My first time ever seeing this, just grand!

New to Confluence, and amazed that it is missing this as a native feature. I see that there is a 3rd party add on that is attempting to fix. Has this all but been abandoned by Atlassian?

Thanks for filling me in, cheers!

Numbered Headings for OnDemand is available in the Atlassian Marketplace, https://marketplace.atlassian.com/plugins/nl.avisi.confluence.plugins.numberedheadings-connect. Currently this is a seperate listing, but we are working on merging it the with existing Numbered Headings (for behind the firewall) listing.

Please note that there are some bugs regarding the TOC macro and Numbered Headings, these will be fixed when a new version of the TOC macro is deployed on Confluence OnDemand.

I'd also be happy to test this.

We are very keen to see support for nested numbered lists in our documentation on Confluence.

Yes please, I'd like to test it

Greg

Begin forwarded message:

From: "Tomas Theunissen (JIRA)" <jira@atlassian.com<jira@atlassian.com>>
Subject: [JIRA] (CONF-1732) Numbered Headings
Date: June 20, 2013 5:47:56 AM PDT
To: <gmcmillan@linkedin.com<gmcmillan@linkedin.com>>

https://jira.atlassian.com/s/en_UKkdyw0-1988229788/6097/9/_/images/icon-jira-logo.png
https://jira.atlassian.com/secure/useravatar?avatarId=10612
Tomas Theunissen<https://jira.atlassian.com/secure/ViewProfile.jspa?name=t.p.theunissen%40avisi.nl> commented on [New Feature] CONF-1732<https://jira.atlassian.com/browse/CONF-1732>
Numbered Headings<https://jira.atlassian.com/browse/CONF-1732>

We have made good progress on making Numbered Headings available on Atlassian Connect. We are currently looking for some people to test it out. If you are interested, please contact me att.p.theunissen@avisi.nl<t.p.theunissen@avisi.nl>

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

We have made good progress on making Numbered Headings available for Atlassian OnDemand. We are currently looking for some people to test it out. If you are interested, please contact me at t.p.theunissen@avisi.nl