With all the respect, but to me CVS is not really Excel, but a collection of data. A comma separated DB dump. The export to Excel feature is gone missing in the latest release, and so do all the Swedish characters and selected columns in the CVS export. It actually produces unreadable results, even after excel function "text to column" has been applied. It also picks random columns to export, so neither options (all columns, selected columns) work properly. Even the previous version did that with Excel, so that bug is still there in our server installation.
The value I get from the CVS export right now is none.
The Excel export was not Excel either, it was XML that says "hey, I'm a spreadsheet".
In theory, I understand why Atlassian has replaced Excel with CSV - CSV was the single most demanded form of export for years, and should make a perfectly good replacement for Excel as spreadsheets can read it just as well as the XML.
However, I don't feel the current CSV export is ready to replace the Excel export yet, with some of your reasons being part of why.
There is one thing though - if you're on server, then look for (you may need to create it) jira-config.properties in the home directory, add jira.export.excel.enabled=true to the file and restart. The old Excel export comes back. Should work up to Jira 7.5 (I've not tried it in 7.6)
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs