Import into Custom Fields for Next-Gen Projects

Sven Delmas May 4, 2020

I have been unable to import any datatype into a custom field. Simple text string, number, label, multi choice. The same fields import fine into a classic project. So is the reality that CSV import into custom fields are just not supported in next-gen projects at this point?

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 5, 2020

Hello @Sven Delmas

Thank you for reaching out.

Indeed, there are some bugs in Jira Next-gen that causes the CSV import/export functionality to don't work as expected. They are caused due to the Next-gen architecture which uses unique identities for each project, so they are not properly mapped in the External system import.

You can check the link below for more details:

Unable to perform direct migration of the project from cloud to cloud due to CSV import bugs with Next-Gen projects 

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

While we work to fix those bugs, a workaround would be to import your issues to a Classic project and use the guide below to migrate to Next-gen:

Migrate between next-gen and classic projects 

Let us know if you have any questions.

Cindy Chan July 24, 2020

I am also facing problems importing short text custom fields onto next-gen projects.

Suggest an answer

Log in or Sign up to answer