Custom fields in next-gen are very limited, there are a lot of types that are not available, so if you are importing a CSV with custom fields not available, it won’t work.
Also, we have some bugs related to CSV import to next-gen, maybe you are facing one of them:
Related to the Parent ID field, currently, it’s not possible to import issues with a parent-child relationship:
Hope this helps!
If you have any other question, please let us know.
Agree with @Cameron.
Next-Gen Projects have a SIGNIFICANTLY long way to go before they become generally useful.
If you cannot perform something as simple as a CSV import when the field names (regardless of whether they are in-built or custom fields) from the CSV MATCH those field names of the Next-Gen project (and you try to MANUALLY map the values yourself), then this effectively becomes useless to anyone wanting to take advantage of a simpler approach proposed by Next-Gen projects.
Importing only non-custom fields (which seems to be the case at the moment) is utterly unacceptable, IMO, as it stands right now.
At the moment you can't even import simple TEXT (custom) field data...that isn't MAPPING, it's a simply copy/paste operation, which is what you'd be doing with the Summary/Description fields (which appears to be all that's even working at the moment).
Hi @Ollie Guan ,
Thanks for the response. Unfortunately, the post you shared does not answer my question. I am comfortable importing via CSV and have already done so. The options in next-gen are extremely limited compared to standard and I can't import:
1. Custom Fields
2. Parent ID field continually bugs out
My primary concern is the first as the second can be manually once the issues are created by bulk assignment.
Hi @Cameron Thom
I want to apologize for this inconvenient, it was a different community leader (not @Ollie Guan) that updated the title of this question. His intention was to make it more searchable through tags. The Nex-Gen part (which was in between square brackets) was removed and the nex-gen and nexgen tags were added instead.
The token [Nex-Gen] in between square brackets was also something that could create issues for mailing lists of the community platform.
We are working on a better way to communicate such changes to avoid this friction. The community leader that updated the content didn't want to inform you about the change because that would require answering the question which would take your chances to get an answer to your inquiry.
I hope that clarifies why you noticed this change.
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