Using CSV import, is there a way to import indented bullet points in the description field?

[len sheppard]

I am using the non-admin CSV import.  For the description field, I can import bullet points by using asterisks, which get converted to bullet points.  I haven't found a way to indent some of the bullet points, however (like the 3rd row in the list below).  I've tried the following with no success:

• adding blank spaces before the asterisk
• putting things in front of the asterisk 
  • \\ followed by blank spaces
  • blank spaces inside quotation marks
  • preceding the asterisk with the characters "<tab>"

[Petter Gonçalves · Accepted solution]

Hello @len sheppard

Thank you for reaching out.

The CSV importer respects the syntax provided by the Wiki Style renderer previously used on Jira Cloud. That being said, you must add the asterisks two times (**) to properly indent a bullet point in Jira Text fields through CSV, as displayed in the example below:

Also, the same logic should work to add more levels (***, ****, etc). Can you please confirm if it properly works for you?

For more details about Jira syntax for CSV import, you can check the documentation below:

Text Formatting Notation Help 

Have a nice weekend!

[TC]

When I try to use this formatting, it doesn't step it down to multiple lines. When I do a line or paragraph break, it doesn't create the bullets. Any idea how to fix that? 

[Christoph Schmitz]

Hey @TC ,

did you manage to get this rolling? I need to import bulletpoints in description aswell.

Best regards
Christoph

[len sheppard]

Hi, Petter.  Your original answer worked great!  Now, a few years later, it has stopped working.  When i import in a description field the following:

* bullet 1st level

** bullet 2nd level

I get the following:

* bullet 1st level** bullet 2nd level (with no actual bullet points, just the asterisks)

Do you know what might have changed or I am doing incorrectly?

[len sheppard]

We solved the problem actually.  We had accidentally marked the field as "map data".  Undoing that checkmark during the import process resolved the problem.