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

Hi all, late update to inform y'all that this ticket is being closed. The feature was rolled out to production earlier this year and has implemented the scope outlined in the description of the ticket.

I have created a separate ticket to capture the follow-up requests to maintain numbering across split numbered lists: https://jira.atlassian.com/browse/CONFCLOUD-77081

As of now, the work for this follow-up ticket is unlikely to be picked up anytime soon. However, the team will continue to monitor the ticket for customer demand to inform future prioritisation.

Thanks all,
Ethan

👋 Hi all, Ethan from the Atlassian Editor Team here. As always, thank you for the continuous feedback on how we may improve the editing experience in Confluence, and the wider Atlassian product suite. I wanted to share that our team has been reviewing the feedback for this issue, and are keen to solve for ways of enabling authors to format lists to their liking, without breaking the numbering of an ordered list. 

We recognise this issue presents a significant challenge to create professional looking documentation, particularly when more complex sequencing of content is required. The current workaround of using shift + enter to create a newline to support the insertion of content without disrupting the numbering isn’t suitable for nodes which can’t currently be nested in lists at all (e.g. tables, panels, expands etc.).

From the feedback, we are focusing on addressing the following use cases:

1. Ability to start an ordered list from any number
2. Ability to continue the numbering in lists when split 

What is not under consideration for the scope of this current project is to support nesting of more content types in lists. Whilst there may be legitimate use cases to support for additional nesting (e.g. macros in lists), we recognise the core of the problem is primarily not wanting to break the sequence/count of a numbered list, especially with non-text content.

My team and I are exploring a few backwards compatible approaches at the moment that are aimed at not breaking existing content/storage formats, and aligned with interaction patterns you’ve come to expect from other notable rich-text editors. To ensure we’re on the right track, I invite you to schedule some time with my team and I to provide feedback on our approach and working assumptions using my 30 minute meeting link.

Thanks all and stay safe,

Ethan