Hi all,

Unfortunately, we had to pause the work on the new CSV export for a while. The good news is that we have picked up that work again and we are actively working on getting it shipped in JIRA.

Consequently, this issue will be gone with the new export functionality as per Bartek's previous comment. Please do watch https://jira.atlassian.com/browse/JRA-32352 for updates on the progress of the CSV export work.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

It seems like @Bartek doesn't work at Atlassian anymore or his username changed - There is "(Inactive)" in his username now.

If someone else from Atlassian is seeing this, it would be great if you could answer and/or reopen this task.

@Leif I completely agree however I don't have the access ability to reopen.

Wouldn't it be better to reopen this issue, with all the history, rather than duplicating/cloning it?

@here I have cloned this issue to reopen the investigation. Please vote for this issue here:- https://jira.atlassian.com/browse/JRA-60088

I also like to know if this is already implemented for the server version of JIRA.

@Bartek: Do you have an update/ETA on this?

Hi @Barek. I've searched for the CSV export option in JIRA but don't see it anywhere. Has this been implemented? If not what is the rollout date? This is an issue I'm keen to resolve.

Thanks for the update, Bartek. That sounds promising. We're looking forward to the new version.

Once changed from HTML to CSV, will Excel be able to interpret the data types when opening the exports and formatting the data cells/columns accordingly?

E.g. if the user exports from JIRA a date/time column, will this column be recognized by Excel a date field?

Hi All,

Thank you so much for your comments. We do read all of your feedback, but it is not always possible to respond to all of these comments in a timely manner.

The very problem that you have referenced in this issue is in fact one of the many problems related to the Excel export. It is also unique to the very way how this feature works today. In fact if you look closely the Excel export is in fact a HTML export behind the scenes, and it relies on the fact that MS Excel is capable of translating the HTML format into a spreadsheet. This very assumption of using HTML is in fact the very reason why this feature is not meeting our quality standards any more.

And so we have decided to remove it.

But before you raise an alert, please read on, because obviously that is not how we want to deal with the wider need of JIRA providing an actionable export.

What we are working on (as I write this response) is a completely new JIRA export feature. It will allow for the data to be exportable to Excel but in a much more convenient way, because behind the scenes it will use a CSV file format (comma-separated value) which is a de-facto standard adopted by many other spreadsheets and tools. It is also a very popular format amongst numerous scripting solutions and above all it is human readable and editable in any text editor.

Implementation of CSV export is planned to be performed in several stages. Within the next several weeks you will see an experimental beta-release of this feature to our Cloud instances. It will also be released as an experimental feature to Server customers slightly later. We then plan to spend the next several months on refining and polishing the CSV export, in order to replace the current HTML export with CSV export later this year. Until then both CSV and HTML export will exist in parallel. Possibly the HTML export will be left in the product a bit longer as a dark feature, for those customers who need to adjust their internal procedures before migrating from HTML to CSV based export.

Thanks again for your continued feedback related to this topic. I hope the news I have just shared is a good one.

Cheers,
Bartek
JIRA product manager