Even a webapp where I don't pay a penny for has this feature: Google Keep, you just paste a text with break lines and each line from the pasted text creates a new action item or whatever you want to call it.

The Jira editor really sucks, and the are bugs that have been happening for months if not years, like some time adding an image and the editor says it doesn't recognize it, but adding the image once the ticket was created does work 🤷‍

In the past, I used to complain about a lot of bugs in tickets like this, this year may be the first, but not because the bugs are gone, but because it takes time, and whatever you report can be in the backlog for years, like this one.

This is a frequent annoyance to us also.  I have to click and click and copy and paste to change notes and bullets into action items.

THE OBVIOUS BEHAVIOUR IS TO CLICK ON THE LINE, AND CLICK THE ACTION ITEM ICON.  (Like in Server!    I often regret that we got pushed onto Cloud from our Server - this is one more example of the software not doing the correct thing.)

With the Didit Checklist app you can turn a list of bullet points into a checklist either by using the AI generator that looks at the Confluence page and turns the content into a checklist, or by simply copying & pasting the list of bullet points into a new checklist. 

Still an issue in January 2023. I will add that the issue appears to not just be with converting lists to action lists. Selecting multiple rows of normal text also fails to create an action list. Quite a nuisance to have to create an action list one line at a time

Yes, they basically removed essential functionality and then called it a feature request. I have a feeling that confluence is moving backwards. Frankly I can not name a single feature in confluence added in the last 2 years, that I use. Meanwhile I still struggling with their abysmal new editor, that is still lacking features their old editor had.

This product is simply regressing in functionality. What a shame

I was not that keen on using confluence, but tried to go over the barrier of using a new tool. 
Finding out that something a "stubborn user as myself " would consider basic functionality to be a bug reported for 2 years and then considered a feature request, woaahh... That frustrates me enormously. I try to put my emotions and frustration aside, but not being able to do something that feels so simple and basic is just crazy to swallow for me.

I don't want to spread hate in my words in any way. I would just like to communicate that for me such a small but seemingly basic feature missing (broken, whichever words one chooses to use) is a tipping point not to use a product anymore and give an alternative a try or even to advocate another tool inside my organization.

Good luck to all of you here who have it harder to switch tools.

I like bullet points and I like checking boxes and my inability to combine the two saddens me

 it seems that we have a feature request in disguise here. 

Imagine if you lost your arm in some sort of industrial accident, and then went to the ER and they said, "you want another arm? that sounds like a feature request in disguise..."

feature request are for new things, Tamim, NOT for things that used to work but you forgot to port the functionality over to your cloud product. 

I see this has been looked and at it's been converted to a feature request rather than a bug. 

This is dissapointing given this is a feature of the old editor and the new editor does not support it.  So I question if feature parity and supporting existing user workflows is really a feature request or actually a bug in the new editor.

I echo Adam about this bug. This bug is also affecting my org. Is there any update about prioritization about this bug?