Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

problem importing from CSV

ddlaer0
Contributor
February 16, 2024

Importing from a .csv file is problematic. 

When creating a database automatically some fields are already created and some empty entries are added. Could there be an option to directly create a new database from file?

Further, now there is no way to automatically set the field names to the header row of the imported file. So you have to enter/copy the field names manually. When entering a name, you have to create that field by clicking the + Create new text field.... button. And you have to do this for all fields you want to import.

Screenshot 2024-02-16 at 09.43.00.png

It would already help if all fields would have a default "text type" and a default name not conflicting with other fields. When clicking the Apply button, you cannot continue until all field names are set to different names.

But... after creating/setting all fields with the desired name and continuing I get:

Screenshot 2024-02-16 at 09.43.56.png

So all my changes to the field names were gone and default names were given to the different fields...

 

3 answers

Suggest an answer

Log in or Sign up to answer
0 votes
scott.brinley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 24, 2024

This oversight is frustrating and wastes a lot of time.  I need to quickly create these databases without manual steps for a very large data migration project.  

0 votes
Federico Magnolfi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 22, 2024

Same problem here, this issue is ridiculous, I can't believe there is no way to use the first csv row as header.

A simple checkbox "use first row as header" would be enough.

Right now, we are wasting a lot of time with manual copy and paste for every column 

0 votes
Claude
Contributor
March 8, 2024

Yep, this is so frustrating. I don't understand the logic behind forcing you to fill out the header fields if they are ignored anyway on import.

TAGS
AUG Leaders

Atlassian Community Events