Redmine

If I may, I request that feature.

The request to have all fields available in the CSV was that the CSV feed at that time contained fields that there was no to get on report. Since some fields could not be placed on a report, the only way was to get a complete export and build our own report. This worked fine, and the customers could get what they wanted, even if it had some extra steps.

With the improvements in the reporting, the users can now generate the report they want without the extra steps. As long as the reporting keeps improving, this feature may not be as necessary. Things such as wrapping titles in the PDF (#4686) will all help the users get the reports in the format they want without having to perform extra steps.

Hello,

I just wanted to raise an issue about the same problem, but before I found this issue here.
It exists since 1 year and the problem still exists. PDF export works fine but CSV
doesn't. I would embrace it if this will be fixed soon. Or does someone know why this is not fixed yet?

Hello,
I have one more problem with this export. The field "Description" is export too. It usually contains a long descripton with many CR-LF characters. During export all this CR-LF are put to CSV file. In consequence a CSV file is very irregular. Well, I thought the use of Custom query in export can resolve this problem (this field is not necessery for me in CSV). I wonder if it is a problem for You. I am a new user of Redmine.