CSV export fails when issue has too much text
Large issues created either by filling the maximum description length a few times, or from REST issue insertion can break the csv output.
The symptom is that the text of the description overflows into the first column, breaking the one row per issue assumption of csv.
Manually editing the issues to move the excess text into attachment works around the problem.
[ Many thanks for an otherwise great product ]
Updated by Etienne Massip over 12 years ago
There is no columns in CSV format, only fields values separated by commas or semi-colons.
What you're describing looks more like an issue with the piece of software used to read the CSV file.
If you are sure it is not, then could you please post an example of a bad formatted file ?