Importing data from Tuleap to Jira

[Andre]

Hi all, I'm trying to do some data migration between Tuleap and Jira. I've tried both CSV and JSON methodologies in order to import the hierarchy Sprint > Story > Task and Sprint > Bug without any luck.

We have configured a Jira Next Gen project. The issues we have found are:

1. Impossibile to set the issue type
2. Impossibile to set the associated sprint for a story
3. Impossible to set the release for a story

Thank you.

[Dario B · Accepted solution]

Hello @Andre ,

Next-Gen projects have been introduced not too long ago and are still under heavy development. So, at this current point in time, there are still bugs and missing functionalities that are preventing you from achieving your goal:

• [JRACLOUD-72655] CSV imports does not map Issue types for Next-gen 
• [JSWCLOUD-17829] NextGen - CSV Import - Failed to assign Epic as IssueType 
• [JRACLOUD-72091] As a Jira admin, during the CSV External System Import to a Next-Gen project, the mapping of the "Issue Type" value and the "Story Point Estimate" value is not respected
• [JSWCLOUD-17758] Ability to import issues with parent-child(epic-task) relationship to next-gen project
• [JRACLOUD-70949] CSV import will fail if Next-gen custom field is mapped
• [JSWCLOUD-18048] Dropdown custom field type on next-gen project doesn't allow a value via CSV import 
• [JRACLOUD-73628] Next-gen CSV Import - cannot import data into "Paragraph" field 

You may want to vote and set yourself as a watcher to the above issue so that you will be notified in case of any update.

As a workaround, you may want to try to import the issues into a Classic project and then migrate them to a Next-Gen project as explained in:

• Migrate between next-gen and classic projects 

Also, in order to know the functionalities that are going to be released, you can check the public roadmap using below link:

• https://www.atlassian.com/software/jira/whats-new/next-gen#intheworks

However, it has also to be mentioned that Next-Gen projects are designed to be a simplified version of the Classic Jira Software projects (and JSD) and are intended to be used by people that need to be able to start working without having to configure too many things.

Therefore also after all the bugs will be fixed and functionalities implemented, there are still chances that using Classic project will still be the best option for integrations.

For further details see also:

• Everything you want to know about next-gen projects in Jira Cloud
• Working with next-gen software projects (specifically, review the section named "Classic vs next-gen Jira Software - What's the difference?")
• Migrate between next-gen and classic projects

Cheers,
Dario

[Andre]

Thank you, Dario!