Before we started using Confluence Server a few years ago, on long lists of procedural steps I would break the long step list into more manageable sub-procedure sections separated by un-numbered headings. Using the documentation-intelligent / documentor-friendly program, Adobe FrameMaker, I could end one sub-procedure at step X, insert a heading line, and then manually begin the following sub-procedure with step X+1. But of course the ability to choose the start number of a particular numbered step is beyond the ability of Confluence Server, so I settled on the make-due habit of incorporating my sub-sections' headings into the long numbered list as numbered items themselves. Now, with our forced conversion to Confluence Cloud (and, I assume, eventually to its new editor) it seems only apt that even this work-around will end up screwy. It is not surprising to see this on an editor that requires unintuitive hoop jumps to create a simple nested bullet list within a numbered list.
Before we started using Confluence Server a few years ago, on long lists of procedural steps I would break the long step list into more manageable sub-procedure sections separated by un-numbered headings. Using the documentation-intelligent / documentor-friendly program, Adobe FrameMaker, I could end one sub-procedure at step X, insert a heading line, and then manually begin the following sub-procedure with step X+1. But of course the ability to choose the start number of a particular numbered step is beyond the ability of Confluence Server, so I settled on the make-due habit of incorporating my sub-sections' headings into the long numbered list as numbered items themselves. Now, with our forced conversion to Confluence Cloud (and, I assume, eventually to its new editor) it seems only apt that even this work-around will end up screwy. It is not surprising to see this on an editor that requires unintuitive hoop jumps to create a simple nested bullet list within a numbered list.