I'm not sure about importing directly to an existing next gen project, but as a workaround you could import the issues into a normal Jira project then move them over to the next gen project as specified in this documentation:
Hope this helps!
How about copying the issues instead of moving them? There are some people who said they did that here:
Look at Joshua Sabol's comment
Works for me - need to use in my CSV:
and in my config.txt
We had to abandon assigning the imported tickets to a Sprint because the Sprint field seems to require an ID, not the name.
I am adding this in case other users are going to search for a way to do so.
Importing issues from CSV to next-gen projects is possible as long as you don't map any custom field in the Next-Gen project. This is because of the below bug:
Please review above bug ticket for details.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events