This is a popular and valuable idea and has been combined with CONF-1732. We will consider it for a future release.

If you would like to review our method for selecting features for releases, please read this:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Resolving Duplicate CONF-1929 to CONF-1732. 71 votes from CONF-1929 should be considered added to CONF-1732.

THIS FEATURE IS CRITICAL FOR LINKEDIN'S ENGINEERING TEAM. PLEASE IMPLEMENT SOON. ENGINEERING DESIGN SPECIFICATIONS REQUIRE AUTO-NUMBERED HEADINGS. THIS FEATURE REQUEST SHOULD BE A HIGH PRIORITY NO BRAINER FOR THE ENGINEERING COMMUNITY, AND THE PM IN CHARGE AT ATLASSIAN. WHAT'S THE HOLD UP ATLASSIAN?

AT LINKEDIN, NOT HAVING THIS BASIC FEATURE WILL DRIVE US TO CONSIDER OTHER SOLUTIONS.

It is very inconvenient not to have this. I'm trying to move from document-based requirements and specs and this is a very fundamental text-processing function. I have to manage my lists manually now and updating can be time-consuming and introduces errors.

Hi Ovidiu,

The related issue CONF-1732 is 14th on the most popular issues list. Unfortunately we don't have an ETA as this feature is not on our roadmap at present. Please vote for these issues as it is the best way to get them onto the Confluence roadmap and scheduled for implementation.

Chris

Critical issue for us as well.
We purchased Confluence and started to using it, but right now I'm evaluating MediaWiki (they have a solution - not ideal, but closer than none) to switch to (this being the major complaint internally).
Any ETA on this in Confluence?

This does seem a critical oversight. I know we can't use Confluence until we can have outline numbering. Ideally, it would be the smart outline numbering of my dreams, which handles paragraphs intelligently/etc. But even if it's not, it'll be something. Until I can do outlines, I can't use confluence for speccing.

This is critical for us as well, as we are also transitioning requirements docs to Confluence, and lack of this numbering style will, unfortunately, prohibit us from doing so. Is there any possible workaround?

FYI, other Wikis do this. MediaWiki, for one, that is used for the Wiki Encyclopedia...

How do they do it?

Definitely would be nice. There are lots of outline-specific documents out there use a lot more than 1, 2, 3. We resorted to using the actual numbers, and you can imagine how hideous it looks without indentation.

I'm not even sure the V2Renderer (CONF-2097) will address this type of nesting.

I've recently wondered out loud if a macro could be written to handle the indentations, using tables and whitespace. For example, if I wrote a macro called

, I could pass in parameters that told me how much to indent. The user would have to handle the numbering yourself, but that's no big deal since my users already do I could then determine the indentation amount programatically based on the number of digits or periods in the list.

I.e.,

would add a 3-column, 1-row table:

• 35-pixel blank column
• 20-pixel column with the number "4.2"
• remaining-width column for indented line item

while

would add a 4-column, 1-row table:

• 35-pixel blank column
• 35-pixel blank column
• 20-pixel column with the number "4.3.10"
• remaining-width column for indented line item

The big question would be, how to terminate the macro. You could use a closing macro tag, but that seems more than a little awkward. None of this seems like ideal functionality outside the renderer.