Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-7794

Implement a feature that allows to continue numbering on numbered lists

    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Status Update 27 Nov 2023

      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

      Status Update 18 Oct 2022

      👋 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

       

      Currently, in the rich text editor, if one uses a number list and then uses, say, a bullet, and then continues with a number list, the numbering restarts. We would like to be able to continue the numbering when that happens.

      Summary

      When using numbered lists we, as a user, might need to insert complex text formatting between list numbers. Currently, this is only possible by using the SHIFT+ENTER method, which indents the text.

      Why is this important

      Numbered lists may require complex text formatting within each list number (technical documents for example) and using the SHIFT+ENTER option indents text and can break the visual parameters needed for the documentation.

      Also, having a feature that allows the user to simply determine that the numbered list count should start from where it left prior to this moment is easier than using SHIFT+ENTER with each line break.

      Workaround

      Use SHIFT+ENTER to create a new line without affecting the numbering.

        1. Screen Recording 2023-02-07 at 1.31.02 pm.mov
          16.26 MB
        2. Screen Recording 2023-02-07 at 1.40.48 pm.mov
          7.01 MB
        3. screenshot-1.jpg
          screenshot-1.jpg
          119 kB
        4. screenshot-2.jpg
          screenshot-2.jpg
          45 kB
        5. Screenshot 2023-02-07 at 1.34.15 pm.png
          Screenshot 2023-02-07 at 1.34.15 pm.png
          247 kB
        6. screenshot-3.jpg
          screenshot-3.jpg
          117 kB

            [CONFCLOUD-7794] Implement a feature that allows to continue numbering on numbered lists

            I believe it's not. I have no idea how Jira QA's can let it go into production.

            Reproduction step:

            • Create numer list,
            • Add the table,
            • Continue numbering then - seems ok.
            • But when you delete some number before the table the number after the table are not updated xD

            Example, after that you have the list (when you delete point 3):

            1.
            2.
            table
            4.
            5.
            ....

            Michał Kukuł added a comment - I believe it's not. I have no idea how Jira QA's can let it go into production. Reproduction step: Create numer list, Add the table, Continue numbering then - seems ok. But when you delete some number before the table the number after the table are not updated xD Example, after that you have the list (when you delete point 3): 1. 2. table 4. 5. ....

            Just tested this again on Jira Cloud and at last it seems to be fixed! Didn't test exhaustively but the basic scenario of inserting a table inside a numbered list, and starting a new list from an arbitrary number now work.

            Dwight Holman added a comment - Just tested this again on Jira Cloud and at last it seems to be fixed! Didn't test exhaustively but the basic scenario of inserting a table inside a numbered list, and starting a new list from an arbitrary number now work.

            @Ethan - do you know when this feature will be available in Jira Cloud? Is there a routine process for editor changes to be 'ported' over to Jira?

            Dwight Holman added a comment - @Ethan - do you know when this feature will be available in Jira Cloud? Is there a routine process for editor changes to be 'ported' over to Jira?

            Ethan Yew added a comment -

            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

            Ethan Yew added a comment - 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

            I believe there is a better workaround than inserting a line break.

            My solution involves inserting an actual paragraph into an <li> element.

            I do not know whether this solution works on Cloud. I have only used it on Server.

            Let us assume that you wish to include some additional content inside an <li> element. This content might be simply a paragraph, an image, or a macro.

            To do so:
            1. When you are at the end of the line in a list item, press Ctrl+Shift+D. This shortcut opens the Insert markup window. Obviously, you can also open the window from the menu but it takes more time.
            2. In the Insert markup window, enter any text (for instance, 'asd') and click the Insert button.

            Now, the text that you have entered is added as a paragraph which is part of the <li> element. You only need to backspace the random text and replace it with the desired content.

            Disclaimer: Once again I emphasise that I have only tested this solution on Server. Thus, if you use Cloud, you need to double-check it there. This is particularly important if you use Confluence to generate output in various formats. In such a case, test the output to see whether the solution works as intended.

            Adam Turlej added a comment - I believe there is a better workaround than inserting a line break. My solution involves inserting an actual paragraph into an <li> element. I do not know whether this solution works on Cloud. I have only used it on Server. Let us assume that you wish to include some additional content inside an <li> element. This content might be simply a paragraph, an image, or a macro. To do so: 1. When you are at the end of the line in a list item, press Ctrl+Shift+D. This shortcut opens the Insert markup window. Obviously, you can also open the window from the menu but it takes more time. 2. In the Insert markup window, enter any text (for instance, 'asd') and click the Insert button. Now, the text that you have entered is added as a paragraph which is part of the <li> element. You only need to backspace the random text and replace it with the desired content. Disclaimer: Once again I emphasise that I have only tested this solution on Server. Thus, if you use Cloud, you need to double-check it there. This is particularly important if you use Confluence to generate output in various formats. In such a case, test the output to see whether the solution works as intended.

            @Piotr Starzyk

            Thank you for posting your .gif. I didn't think to try to delete and manually re-type the first number in each section to re-adjust the numbers. I was right clicking on the numbers trying to find some menu for restarting them and couldn't find an option. The fact that we can do what you are showing makes the situation much more tolerable, and I feel better about this update. I do wish the separate sections stayed in sync, but this is still much welcome progress!

            erik.unangst added a comment - @ Piotr Starzyk Thank you for posting your .gif. I didn't think to try to delete and manually re-type the first number in each section to re-adjust the numbers. I was right clicking on the numbers trying to find some menu for restarting them and couldn't find an option. The fact that we can do what you are showing makes the situation much more tolerable, and I feel better about this update. I do wish the separate sections stayed in sync, but this is still much welcome progress!

            @erik.unangst I checked it out and you're right.  The link between the numbers gets lost, and you do have to manually adjust the first number in each disparate section.  Yes, it is a bit disappointing, but after all these years, at least it's some progress.  I made a gif of the lost link issue:

            Piotr Starzyk added a comment - @ erik.unangst I checked it out and you're right.  The link between the numbers gets lost, and you do have to manually adjust the first number in each disparate section.  Yes, it is a bit disappointing, but after all these years, at least it's some progress.  I made a gif of the lost link issue:

            erik.unangst added a comment - - edited

            I'm excited to see that some progress has been made here!

            However, I am finding an issue with the implementation.

            From what I can tell, you can now insert items like tables/macros/pictures into a numbered list and keep the numbering. Unfortunately, this appears to break the link between the numbered items preceding the insert and the numbered items following the insert. So, if I want to add/delete another number above a macro insert, then the numbers below the macro insert will not update.

            With the current implementation, it seems like any modifications to a numbered list like this would necessitate re-creating most if not all of the list. Maintaining long lists used for technical documentation would seem to be a nightmare with the way it works now. Am I missing something?

            Don't get me wrong, it is great to see this progress to the editor, but I am disappointed that it still does not appear to offer the same numbered list functionality as other common text editors. 

            erik.unangst added a comment - - edited I'm excited to see that some progress has been made here! However, I am finding an issue with the implementation. From what I can tell, you can now insert items like tables/macros/pictures into a numbered list and keep the numbering. Unfortunately, this appears to break the link between the numbered items preceding the insert and the numbered items following the insert. So, if I want to add/delete another number above a macro insert, then the numbers below the macro insert will not update. With the current implementation, it seems like any modifications to a numbered list like this would necessitate re-creating most if not all of the list. Maintaining long lists used for technical documentation would seem to be a nightmare with the way it works now. Am I missing something? Don't get me wrong, it is great to see this progress to the editor, but I am disappointed that it still does not appear to offer the same numbered list functionality as other common text editors. 

            Ethan Yew added a comment -

            Hey 6e687f59fb46 thanks for reaching out. There are some loose ends we're still looking to wrap up with regards to mobile support, however we've actually silently rolled this feature out to the majority of Atlassian customers using Confluence Cloud. We anticipate in some cases, this feature may be able to assist with the migration of content from Confluence Server, with some slight restructuring of the original document. However, I can't guarantee this will work in all cases. 

            Ethan Yew added a comment - Hey 6e687f59fb46 thanks for reaching out. There are some loose ends we're still looking to wrap up with regards to mobile support, however we've actually silently rolled this feature out to the majority of Atlassian customers using Confluence Cloud. We anticipate in some cases, this feature may be able to assist with the migration of content from Confluence Server, with some slight restructuring of the original document. However, I can't guarantee this will work in all cases. 

            Hi Ethan - do you have an update on availability of this server functionality in Atlassian Cloud?
            Are there any plans to leverage this feature to render content migrated from Confluence Server or Jira Server?

            Dwight Holman added a comment - Hi Ethan - do you have an update on availability of this server functionality in Atlassian Cloud? Are there any plans to leverage this feature to render content migrated from Confluence Server or Jira Server?

            Is adding a table into a numbered list going to be something implemented here? The shift + enter method doesn't seem to be working on any of the cloud instances I've tried it on. 

            Benjamin Riester added a comment - Is adding a table into a numbered list going to be something implemented here? The shift + enter method doesn't seem to be working on any of the cloud instances I've tried it on. 

            Plain text markdown does this by default... Just sayin...

            Chris Riggs added a comment - Plain text markdown does this by default... Just sayin...

            Ethan Yew added a comment -

            Hey 9eae0e898c91 no configuration required on your end to opt in to the EAP, more a matter of us making sure to turn it on for the right instance(s). If you're still interested I encourage you to book some time in my calendar to chat through this and get the process going.


            Hey 75f3e0bc41b1 I notice you've posted this comment across a few other editor-related tickets as well. My team and I are open to listening to any of your concerns (relating to this feature request or otherwise) which may or may not have already been raised with our Support team. 

            Ethan Yew added a comment - Hey 9eae0e898c91 no configuration required on your end to opt in to the EAP, more a matter of us making sure to turn it on for the right instance(s). If you're still interested I encourage you to book some time in my calendar to chat through this and get the process going.  Email:  eyew@atlassian.com  Calendly:  https://calendly.com/eyew/30min Hey 75f3e0bc41b1 I notice you've posted this comment across a few other editor-related tickets as well. My team and I are open to listening to any of your concerns (relating to this feature request or otherwise) which may or may not have already been raised with our Support team. 

            Dear Atlassian,

            My IT VP just stopped by my desk (again).  He and I are both pro-Confluence (Server version). He and the leadership team are, however, VERY CONCERNED about the user experience and significant loss of functionality since our move from Server to Cloud.

            WARNING
            There's talk of moving our 600+ users off of Confluence Premium, cancelling, and moving to another platform.  (This isn't a threat. I'm just passing along honest information from our decision-makers.)

            Atlassian, please take quick action on this and other Confluence editor issues! Please, AT LEAST give us back the functionality we had in the Server version.

            Thank you,

            Mark

            Mark B Wager added a comment - Dear Atlassian, My IT VP just stopped by my desk (again).  He and I are both pro-Confluence (Server version). He and the leadership team are, however, VERY CONCERNED about the user experience and significant loss of functionality since our move from Server to Cloud. WARNING There's talk of moving our 600+ users off of Confluence Premium, cancelling, and moving to another platform.  (This isn't a threat. I'm just passing along honest information from our decision-makers.) Atlassian, please take quick action on this and other Confluence editor issues! Please, AT LEAST give us back the functionality we had in the Server version. Thank you, Mark

            If it's as easy as toggling some feature checkbox in settings on our end, then we'd be interested (we're using cloud version of Confluence)  If it's more involved than that, we'll just wait a few more months I guess.  Thanks.

            Piotr Starzyk added a comment - If it's as easy as toggling some feature checkbox in settings on our end, then we'd be interested (we're using cloud version of Confluence)  If it's more involved than that, we'll just wait a few more months I guess.  Thanks.

            Ethan Yew added a comment -

            Hey 9eae0e898c91 optimistically within the first half of this year, we're still ironing out some issues which affect cross-platform usage (i.e. editing in mobile). That being said, if there is sufficient interest from customers like yourself in trying out this feature earlier, we are exploring the possibility of turning this on for select customer instances as part of an early-access-program (EAP). Caveat of course being fixes for some edge cases may not have landed yet (i.e. mobile editing). If this interests you, definitely leave a comment here, or reach out via my email at eyew@atlassian.com

            Ethan Yew added a comment - Hey 9eae0e898c91 optimistically within the first half of this year, we're still ironing out some issues which affect cross-platform usage (i.e. editing in mobile). That being said, if there is sufficient interest from customers like yourself in trying out this feature earlier, we are exploring the possibility of turning this on for select customer instances as part of an early-access-program (EAP). Caveat of course being fixes for some edge cases may not have landed yet (i.e. mobile editing). If this interests you, definitely leave a comment here, or reach out via my email at eyew@atlassian.com

            @Ethan Yew  I can't believe after all these years we are finally seeing actual progress. What's the ETA on this being available to use?

            Piotr Starzyk added a comment - @Ethan Yew  I can't believe after all these years we are finally seeing actual progress. What's the ETA on this being available to use?

            Ethan Yew added a comment -

            Hi all, providing a quick progress update from my team to enable continuous numbering in the Editor. You can see a preview of the upcoming functionality to start an ordered list from any number, and not breaking the sequence of the list, in the videos below.

            Screen Recording 2023-02-07 at 1.40.48 pm.mov

            Screen Recording 2023-02-07 at 1.31.02 pm.mov

             

            The team is currently dogfooding this functionality on our internal instances and performing quality assurance testing to ensure that what we release to production is of a high quality. This may take a few months to reach your instance, and we will share more details on this closer to the time of the actual rollout.

            If you have any further questions or feedback to share on this topic, feel free to reach out to my team and I via email, or my Calendly link below:

            Ethan Yew added a comment - Hi all, providing a quick progress update from my team to enable continuous numbering in the Editor. You can see a preview of the upcoming functionality to start an ordered list from any number, and not breaking the sequence of the list, in the videos below. Screen Recording 2023-02-07 at 1.40.48 pm.mov Screen Recording 2023-02-07 at 1.31.02 pm.mov   The team is currently dogfooding this functionality on our internal instances and performing quality assurance testing to ensure that what we release to production is of a high quality. This may take a few months to reach your instance, and we will share more details on this closer to the time of the actual rollout. If you have any further questions or feedback to share on this topic, feel free to reach out to my team and I via email, or my Calendly link below:  Email:  eyew@atlassian.com  Calendly:  https://calendly.com/eyew/30min

            Dwight Holman added a comment - - edited

            At present this problem affects Jira Cloud too. We consider this 'gap' (Server functionality not available in Cloud) a blocking issue for our Jira Cloud migration. For us the ability to resume list numbering (e.g. a table or code block inside a numbered list), means description and comment text is not properly migrated.

            This was being tracked in JRACLOUD-75310 but that bug has been closed as a duplicate (although is not linked to this ticket).

            Dwight Holman added a comment - - edited At present this problem affects Jira Cloud too. We consider this 'gap' (Server functionality not available in Cloud) a blocking issue for our Jira Cloud migration. For us the ability to resume list numbering (e.g. a table or code block inside a numbered list), means description and comment text is not properly migrated. This was being tracked in JRACLOUD-75310 but that bug has been closed as a duplicate (although is not linked to this ticket).

            Really pleased to see  this is being progressed. If it is not possible to include a 'Continue numbering' feature in the Confluence Wiki editor can you at least ensure that the MS Word Import feature respects 'continued' numbered lists created in Word documents and imported in. Personally, this would solve most of my own issues. Thanks! 

            Martin Sirl added a comment - Really pleased to see  this is being progressed. If it is not possible to include a 'Continue numbering' feature in the Confluence Wiki editor can you at least ensure that the MS Word Import feature respects 'continued' numbered lists created in Word documents and imported in. Personally, this would solve most of my own issues. Thanks! 

            Ethan Yew added a comment -

            Hi all,

            Officially transitioning this Suggestion ticket to "In Progress".

            Plugging my 30 minute meeting link once again for folks to reach out and chat with my team and I on our planned approach. Definitely want to make sure we're operating under valid assumptions and that our solution addresses the pain points you're actually facing!

            Thanks all and stay safe,

            Ethan

            Ethan Yew added a comment - Hi all, Officially transitioning this Suggestion ticket to "In Progress". Plugging my 30 minute meeting link once again for folks to reach out and chat with my team and I on our planned approach. Definitely want to make sure we're operating under valid assumptions and that our solution addresses the pain points you're actually facing! Thanks all and stay safe, Ethan

            @Ethan Yew 

            This is probably relevant too: https://jira.atlassian.com/browse/CONFCLOUD-25836

            Casey Meijer added a comment - @Ethan Yew  This is probably relevant too: https://jira.atlassian.com/browse/CONFCLOUD-25836

            thx for the update, Ethan

            Christopher Beck added a comment - thx for the update, Ethan

            Ethan Yew added a comment -

            Hi all, 

             

            This is Ethan from the Atlassian Editor Team. 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

            Ethan Yew added a comment - Hi all,    This is Ethan from the Atlassian Editor Team. 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: Ability to start an ordered list from any number 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

            And while I joke about using the pandoc format itself (as it won't solve the issue), consulting with the pandoc developers would surely be a wise move, as document storage formats and conversions between them are their bread and butter: 

            https://pandoc.org/

            Casey Meijer added a comment - And while I joke about using the pandoc format itself (as it won't solve the issue), consulting with the pandoc developers would surely be a wise move, as document storage formats and conversions between them are their bread and butter:  https://pandoc.org/

            Casey Meijer added a comment - - edited

            It's not the core that's the problem.  Even the old confluence wiki format supported this. If anything, it's likely the need to try to maintain cross-compatibility between multiple different storage formats, which is why adding more would only exacerbate the problem.

            The current core storage format is JSON-based I believe.  There's no textual markup format that will compete with that for flexibility.

            It's not really a disagreement.  More of a misunderstanding and frankly, I think reading this again would probably help clarify: https://inessential.com/2009/07/30/anatomy_of_a_feature. A key thing the author of the article missed, is backward compatibility and cross-compatibility, which alone could fill scores of articles of the same length. 

             

            Also, why would I apologize if I wasn't sorry, lol. What an odd accusation. 

            Casey Meijer added a comment - - edited It's not the core that's the problem.  Even the old confluence wiki format supported this. If anything, it's likely the need to try to maintain cross-compatibility between multiple different storage formats, which is why adding more would only exacerbate the problem. The current core storage format is JSON-based I believe.  There's no textual markup format that will compete with that for flexibility. It's not really a disagreement.  More of a misunderstanding and frankly, I think reading this again would probably help clarify: https://inessential.com/2009/07/30/anatomy_of_a_feature. A key thing the author of the article missed, is backward compatibility and cross-compatibility, which alone could fill scores of articles of the same length.    Also, why would I apologize if I wasn't sorry, lol. What an odd accusation. 

            skyzyx added a comment -

            Sorry for the snark

            No you're not, but it's fine. Feel free to disagree with me.

            It just seems like whatever core implementation the current "new" editor is built on is questionable. Commonmark is battle-tested. GFM is battle-tested.

            skyzyx added a comment - Sorry for the snark No you're not, but it's fine. Feel free to disagree with me. It just seems like whatever core implementation the current "new" editor is built on is questionable. Commonmark is battle-tested. GFM is battle-tested.

            The new new editor...  Why not build it on top of Pandocs?

             

            I don't think adding yet another internal document format is the way forward here.  Sorry for the snark  

            Casey Meijer added a comment - The new new editor...  Why not build it on top of Pandocs?   I don't think adding yet another internal document format is the way forward here.  Sorry for the snark  

            skyzyx added a comment -

            Firstly, you can do this in HTML. Which doesn't mean it's easy to build into the editor, but it sets the stage for user expectations.

            Secondly, I think that what the original requestor asked for in 2007 is the wrong thing to implement. Resetting the list at 1 is the right thing to do according to the screenshots posted above.

            However, if the admonition (e.g., info/warn/error block) were nested under the list item, then (a) the association between the admonition and the list item would be clearer, and (b) this whole problem of having to reset numbers goes away.

            As such, see CONFCLOUD-58656, CONFCLOUD-68137, and CONFCLOUD-67862 which could all be solved by (or, at worst, made easier by) basing the core of your editor implementation on GitHub-Flavored Markdown.

            And for any non-engineers who say "this is easy": First, calm yourself. Second, read https://inessential.com/2009/07/30/anatomy_of_a_feature.

            I'm not suggesting that building atop GitHub-Flavored Markdown would be easy. However, as a Principle Software Engineer, I can say that there is a compelling argument which suggests that doing so is the right thing to do for the longevity of the Confluence content editor.

            skyzyx added a comment - Firstly, you can do this in HTML. Which doesn't mean it's easy to build into the editor, but it sets the stage for user expectations. Secondly, I think that what the original requestor asked for in 2007 is the wrong thing to implement. Resetting the list at 1 is the right thing to do according to the screenshots posted above. However, if the admonition (e.g., info/warn/error block) were nested under the list item, then (a) the association between the admonition and the list item would be clearer, and (b) this whole problem of having to reset numbers goes away. As such, see CONFCLOUD-58656 , CONFCLOUD-68137 , and CONFCLOUD-67862 which could all be solved by (or, at worst, made easier by) basing the core of your editor implementation on GitHub-Flavored Markdown. And for any non-engineers who say "this is easy": First, calm yourself. Second, read https://inessential.com/2009/07/30/anatomy_of_a_feature . I'm not suggesting that building atop GitHub-Flavored Markdown would be easy. However, as a Principle Software Engineer, I can say that there is a compelling argument which suggests that doing so is the right thing to do for the longevity of the Confluence content editor.

            Totally agreed, this is a basic feature that needs to be in there. I understand it may be hard to do with the "rich text editor", but frankly I don't like these rich text editors. They try to make things simple, and end up being a pain to implement and maintain. I would way rather use a format like enhanced markdown where it's not a mystery how to do things, and where things like this can be more easily done.

            gary.bisaga@powerschool.com added a comment - Totally agreed, this is a basic feature that needs to be in there. I understand it may be hard to do with the "rich text editor", but frankly I don't like these rich text editors. They try to make things simple, and end up being a pain to implement and maintain. I would way rather use a format like enhanced markdown where it's not a mystery how to do things, and where things like this can be more easily done.

            +1

            Iulian Danciu added a comment - +1

            +1 Absolutely necessary feature!

            Rasa DovydaitienÄ— added a comment - +1 Absolutely necessary feature!

            Seriously? This lack of a basic feature comes from the time of the release of Windows Vista?! That is like the computer equivalent of the Neolithic.

            Tim Williams added a comment - Seriously? This lack of a basic feature comes from the time of the release of Windows Vista?! That is like the computer equivalent of the Neolithic.

            I totally agree with the previous comments. I actually can't believe this hasn't been picked up earlier, this is basic text edition we're talking about - this clearly shows that people managing Confluence improvements priorities don't actually use it themselves, otherwise it would have been done a long while ago !

            Thomas Dargent added a comment - I totally agree with the previous comments. I actually can't believe this hasn't been picked up earlier, this is basic text edition we're talking about - this clearly shows that people managing Confluence improvements priorities don't actually use it themselves, otherwise it would have been done a long while ago !

            > Solving continuous numbering on numbered lists is on our priority list

            Wow.  If an issue that's been sitting on the back-burner for 15 years is on their priority list, I'd hate to see the time-to-fix for issues relegated to other queues.  I also wouldn't hold my breath as far as them ever getting around to fixing it.  What are some good alternatives to Confluence that have this basic feature implemented?

            Piotr Starzyk added a comment - > Solving continuous numbering on numbered lists is on our priority list Wow.  If an issue that's been sitting on the back-burner for 15 years is on their priority list, I'd hate to see the time-to-fix for issues relegated to other queues.  I also wouldn't hold my breath as far as them ever getting around to fixing it.  What are some good alternatives to Confluence that have this basic feature implemented?

            Anxiously waiting for this to be fixed

            Justin Bowen added a comment - Anxiously waiting for this to be fixed

            Ruby Cheng added a comment -

            Pressing shift+enter to insert sentences between two steps is workable, but if I intend to insert a table, the table will just go to the last step.... Is it possible to insert a table between two steps?

            Ruby Cheng added a comment - Pressing shift+enter to insert sentences between two steps is workable, but if I intend to insert a table, the table will just go to the last step.... Is it possible to insert a table between two steps?

            I agree with Gen.  After 15 years, could we at least get a quick fix and be able to set numbering values on a list?  It wouldn't be as dynamic as picking up the list from where the previous one left off, but it would at least all me to quickly and easily fix it myself.

            Jeff Aronow added a comment - I agree with Gen.  After 15 years, could we at least get a quick fix and be able to set numbering values on a list?  It wouldn't be as dynamic as picking up the list from where the previous one left off, but it would at least all me to quickly and easily fix it myself.

            Gen added a comment -

            Fifteen years is a long time for an issue to remain open. Users should be able to insert non-list elements within a list and continue numbering; this is a basic expectation for a dynamic workspace. At the very least, let users set the numbering values when the list numbering is restarted.

            Gen added a comment - Fifteen years is a long time for an issue to remain open. Users should be able to insert non-list elements within a list and continue numbering; this is a basic expectation for a dynamic workspace. At the very least, let users set the numbering values when the list numbering is restarted.

            This is the way. 

            David Franklin added a comment - This is the way. 

            John Leroy added a comment -

            Please implement this. Inexcusable that such basic functionality is not found in Atlassian products.

            John Leroy added a comment - Please implement this. Inexcusable that such basic functionality is not found in Atlassian products.

            Please take care of this feature. Every complex documentation can benefit from it. Thanks!

            Thomas Fischer added a comment - Please take care of this feature. Every complex documentation can benefit from it. Thanks!

            This feature is a must for my team. We're using confluence for documentation and not being able to continue the numbers is a pain! 

            Kimberly Grindle added a comment - This feature is a must for my team. We're using confluence for documentation and not being able to continue the numbers is a pain! 

            JM added a comment - - edited

            It's so sad!

            I was wondering why the screenshots are looking so old! Then I noticed as well that the issue was reported in 2007

            JM added a comment - - edited It's so sad! I was wondering why the screenshots are looking so old! Then I noticed as well that the issue was reported in 2007

            Nicholas Wade added a comment - - edited

            Re: Status update Feb 2022 

            Progress definition of:

            an expression of action in making steps towards a goal, e.g. this ticket (not). 

            Still stuck since 2007 on 'gaining interest'...

            Nicholas Wade added a comment - - edited Re: Status update Feb 2022  Progress definition of: an expression of action in making steps towards a goal, e.g. this ticket (not).  Still stuck since 2007 on 'gaining interest'...

            OMG... just noticed that according to this ticket, the issue was reported in 2007..!!!!

            Nicholas Wade added a comment - OMG... just noticed that according to this ticket, the issue was reported in 2007 ..!!!!

            This feature would be very helpful.  Please consider implementing this soon.

            Rosi (Naomi Rosita) Bajari added a comment - This feature would be very helpful.  Please consider implementing this soon.

            At this point I don't think Atlassian even care anymore.

             

            Eliot Martin added a comment - At this point I don't think Atlassian even care anymore.  

            @pavelpigalov .... I hear you brother

            Nicholas Wade added a comment - @pavelpigalov .... I hear you brother

            @Nicholas Wade, I'm just tired of stumbling on all these over and over...

            pavelpigalov added a comment - @Nicholas Wade, I'm just tired of stumbling on all these over and over...

            @pavelpigalov.... so we can take it you are a 'little' upset mon ami?

            Nicholas Wade added a comment - @pavelpigalov.... so we can take it you are a 'little' upset mon ami?

            Blah-blah-blah, and still this is not resolved, moreover it's even UNASSIGNED.

            Such a shame making your users to wait basic stuff for ages

            pavelpigalov added a comment - Blah-blah-blah, and still this is not resolved, moreover it's even UNASSIGNED. Such a shame making your users to wait basic stuff for ages

            JGibb added a comment -

            I also agree... very well described @Nicholas Wade. 

            I often want to put content in instructions, especially warning or note markups, which can not be done even with the shift-enter work around. I then need to either put all the warnings at the end of the instruction, or use bullet points instead of numbers. Neither of which are ideal.

            This limitation is frustration... continuation of numbering is very basic functionally that you expect to have in any documentation tool. Looking forward to this being remedied.

            John

            JGibb added a comment - I also agree... very well described @Nicholas Wade.  I often want to put content in instructions, especially warning or note markups, which can not be done even with the shift-enter work around. I then need to either put all the warnings at the end of the instruction, or use bullet points instead of numbers. Neither of which are ideal. This limitation is frustration... continuation of numbering is very basic functionally that you expect to have in any documentation tool. Looking forward to this being remedied. John

            I 100% agree with @Nicholas Wade on this. He described the problem very well.

            Brendon Gross added a comment - I 100% agree with @Nicholas Wade on this. He described the problem very well.

            Well I'm glad to see that finally after a couple of years, this problem is being taken seriously. But the images shown, do not fully document the problem:

            • You should not have to do a soft return to incorporate anything in a list (which is the current method)
            • You should be able to include insert /note, and insert /several other objects elsewhere in a list, such as a code block (not just text formatted as code) or paragraph text
            • You should be able to incorporate tables in a sequentially numbered list
            • You should be able to include pretty much any other object that you would normally expect in a sequential list
            • You should be able to include bulleted lists in any sequentially numbered list

            Sequential lists are used primarily for logical order i.e., instructional steps. Instructions require information supporting the instruction i.e., tables, bulleted lists, graphics, etc.. It may mean that a table in a sequentially numbered list is followed by a bulleted list before returning to the numbered list. It may mean that a sequentially numbered list is followed by an insert /code snippet or insert /note. The point being, that to resolve this numbering problem properly, the team must think of the various ways the list may be used.

            I would add, that Confluence could also do with paragraph and heading numbering. There are many instances where numbered paragraphs and numbered heading are required for official regulatory documents. 

             

            Nicholas Wade added a comment - Well I'm glad to see that finally after a couple of years, this problem is being taken seriously. But the images shown, do not fully document the problem: You should not have to do a soft return to incorporate anything in a list (which is the current method) You should be able to include insert /note, and insert /several other objects elsewhere in a list, such as a code block (not just text formatted as code) or paragraph text You should be able to incorporate tables in a sequentially numbered list You should be able to include pretty much any other object that you would normally expect in a sequential list You should be able to include bulleted lists in any sequentially numbered list Sequential lists are used primarily for logical order i.e., instructional steps. Instructions require information supporting the instruction i.e., tables, bulleted lists, graphics, etc.. It may mean that a table in a sequentially numbered list is followed by a bulleted list before returning to the numbered list. It may mean that a sequentially numbered list is followed by an insert /code snippet or insert /note. The point being, that to resolve this numbering problem properly, the team must think of the various ways the list may be used. I would add, that Confluence could also do with paragraph and heading numbering. There are many instances where numbered paragraphs and numbered heading are required for official regulatory documents.   

            Christopher Beck added a comment - - edited

            Adding a Better Code Block, for example. The block cannot be moved into the list

            (( I don't have permission to add a screen shot ))

            Christopher Beck added a comment - - edited Adding a Better Code Block, for example. The block cannot be moved into the list (( I don't have permission to add a screen shot ))

            That's great when first making something, Matthew, but as things change and get updated, it isn't always possible.

            Ben Levenson added a comment - That's great when first making something, Matthew, but as things change and get updated, it isn't always possible.

            The trick is to make sure you have a number after the location you want to insert text/image/etc.

            1. Step one
            2. Step two (step I want to insert after)
            3. Step three

             

            1. Step one
            2. Step two (step I want to insert after)
              Note: Obligatory note text.
            3. Step three

            Matthew Mallard added a comment - The trick is to make sure you have a number after the location you want to insert text/image/etc. Step one Step two (step I want to insert after) Step three   Step one Step two (step I want to insert after) Note: Obligatory note text. Step three

            This is not an acceptable work around because if you start a section that has special notes in it or code insert or other things you cannot continue your numbering scheme. I know there are times it works but there are a lot of times that it doesn't.

            Brendon Gross added a comment - This is not an acceptable work around because if you start a section that has special notes in it or code insert or other things you cannot continue your numbering scheme. I know there are times it works but there are a lot of times that it doesn't.

              b44ee328bea8 Ethan Yew
              2138abefa5c6 Bijan Marjan
              Votes:
              553 Vote for this issue
              Watchers:
              227 Start watching this issue

                Created:
                Updated:
                Resolved: