Import Ideas from non-JIRA sourced CSV file

[Kenneth Paterson]

Is there a specific import format for the "Summary" field when importing as a CSV from a non-Jira data source?

Tried a few different formats in my source CSV but keep getting the following error in the attached screenshot. Error log associates the error with the "Summary" field in my CSV.

[Jacques]

Hello @Kenneth Paterson ,

The general CSV import settings can be found on this page. 

From what I see in the error message it doesn't seem related to the Summary but to a custom field, and probably a numeric custom field.

The Summary field is a text field, so it shouldn't give any issue with a numeric value, however big the number is.

Can you try and import the same csv file, with only the Summary and any other required fields for issue creation? If that works fine, then it's pretty sure that it's another custom field.

Also, I'm guessing that in the error message that you pasted, somewhere you should find the specific custom field name that is giving this error.

Hope this helps,
--- Jacques.

[Kenneth Paterson]

Jacques, thanks for the feedback.

Have been doing some trial and error imports of smaller data sets this morning and adding a field at a time, and was able to identify the issue - you were correct it was not with the Summary field. Thanks for your suggestion.

As a business user and fairly new to JIRA as a platform - I still think these error messages could be clarified to be more intuitive as to where the problem was.

Thanks again

Kenny

[Jacques]

Hey Kenny,

I'm glad I could help. Were you able to figure out which field provoked the error? And how did you solve the issue?

Thanks,
--- Jacques.

[Rohan Swami]

Thanks for the feedback on the error messages @Kenneth Paterson 

and thanks for helping out @Jacques !

[Kenneth Paterson]

Jacques,

Yes, the issue was actually with a field that was a checkbox value in Prod Disc, and I had TRUE/FALSE as the values in the CSV, and when remapped to 1 / 0 in the transformation step it worked fine after that.

All fields now loading with smaller test dataset, and final load of complete dataset planned for end of this week.

Thanks

Kenny