[CSV import] The value can't be added to the custom field

[Clément Chevalier]

Hello,

I got some issue with CSV import. Everything work well except my custom field "Modification", which is a checkbox field. 

It have 4 boxes, "None","New","Modified", and "Carry-over".

In my CSV, I put a column named Modification, and added in this column my information, like "Carry-over" or "Modified".

When I put "Carry-over", everything work well, but if I pu "Modified" or "New", I got this message when I validate the process :

• The value [ {null=Modified} ] can't be added to the Custom Field [ Modification ]. The value [ {null=Modified} ] can't be found or is in the incorrect format
• The value [ {null=New} ] can't be added to the Custom Field [ Modification ]. The value [ {null=New} ] can't be found or is in the incorrect format

I tried to map value by myself, but it don't work anyway.

Anyone know my problem? Sorry if it's a basic thing, I'm new to JIRA.

Regards,

Clément .C

[Srinivas Reddy]

Hi @Clément Chevalier ,
You can try checking if there are multiple fields named "Modification" and the mapping might be missed here. 

[Thomas Schlegel]

Hi @Clément Chevalier ,

maybe you have empty values (or lines) in your csv. Is modification a mandatory field in your Jira? What happens, if you try to map the values by yourself? Same error? 

[Clément Chevalier]

Hi @Thomas Schlegel 

My lines are all filed. Modification is a mandatory field.

Yes, it's the same error...

[Thomas Schlegel]

Maybe the csv is wrongly encoded - make sure, the encoding is UTF-8.

If you are not sure, if your csv-file is UTF-8 encoded, open it in the simple windows text editor and save it again as a new file - when you save the file, you can set the encoding in the save-as-dialog.    

[Thomas Schlegel]

Another attempt:

make "Modification" optional and try to import your csv. If it worked then, you might have issues without a value for the field modification. These are easy to find. 

If there are not many of them, I would edit them manually and then make the field mandatory again. If there are too many, it might give you some more clues about the reason for the error.

Do you have a test project for trying this out? I would highly recommend testing the import in a test project before importing the data into a "real" project.