-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
CSV export from the issue navigator is now available for JIRA Cloud and JIRA Server 7.2.
Dave Meyer
Senior Product Manager, JIRA
Users should be able to do a CSV export from the issue navigator in a way that would be compatible with the CSV Importer. In that way, it'd then be possible to merge JIRA instances and also make exporting to reporting tools more seamless.
At the moment, there's no such compatibility, e.g. comments in each issue need to be concatenated and moved to separate columns in order to be imported back with the CSV Importer.
- is duplicated by
-
JRACLOUD-61891 Exports search results to Excel result in empty sheets due to Microsoft update
-
- Closed
-
-
- Closed
- is related to
-
-
- Closed
-
-
- Closed
[JRACLOUD-8580] CSV Export from the issue navigator
Also, when you export data, the time fields are in seconds, which means to have a meaningful rendering, I have to convert everything back to hours and minutes and seconds, and do this work manually every time every day.
When you look at the data in the query filter before exporting it, the time shows days, hours, minutes and seconds. Allow us to keep this format, as the query results shows it.
As far I can see, it is fixed now. The HTML export options are back. It worked for me this morning. We use Jira Cloud.
Joel R. Gabriel (Jo)
added a comment - The CSV export feature broke the functionality previously available in the export to Excel-HTML. I have not been able to produce my reports since the csv is not extracting it in the format that I need based on the WebUI. Kindly reinstate the old export option (HTML); this can be an alternative to csv rather than replacing it altogether and ending up with this showstopper. Heaven forbid that I need to recreate my report templates and formulae!
Joel R. Gabriel (Jo)
added a comment - The CSV export feature broke the functionality previously available in the export to Excel-HTML. I have not been able to produce my reports since the csv is not extracting it in the format that I need based on the WebUI. Kindly reinstate the old export option (HTML); this can be an alternative to csv rather than replacing it altogether and ending up with this showstopper. Heaven forbid that I need to recreate my report templates and formulae! Hi everyone,
CSV export for filters is now available for JIRA Cloud.
Dave Meyer
Senior Product Manager, JIRA
Hi there!
With add-on JExcel, you can export your issues to CSV!
It gives you an Excel-like interface and totally works like the issue navigator but you can* inline edit everything*!
And its completely free!
Download it from the marketplace:
https://marketplace.atlassian.com/plugins/com.moresimp.jexcel/server/overview
Hope it helps.
Cheers, Mark
Jira gives me the feeling of a very amateur tool. At least, compared to Rally, it is. Rally is more expensive but at least it provides logical features one could expect in a system like this.
I am not happy with Jira up to this point to be honest. Import/Export is basic functionality for bulk data processing.
We have released a new version (1.3) of our Exporter (https://marketplace.atlassian.com/plugins/com.deiser.jira.exporter) plugin that resolve this issue. The new CSV Export feature enables you to export all your issue data (including comments, links and custom fields) from Issue Navigator into the most commonly used exchange format. Data is organized by columns separated by semicolon character (";"). Also is 100% compatible with JIRA CSV file import wizard to ensure that you can import the .csv files into any JIRA project or instance.
We hope you like it and fit your needs. All your feedback will be very appreciated.
Cheers.
With excel export, any "User" type fields would show the user's Name.
With CSV export, only the UserID shows up.
Another example is mentioned above with Time/Date fields.
It's not accurate for Atlassian to be selling the CSV export as a replacement for Excel exports. The functionality is simply not the same.
What is being done to work around or remedy this problem with CSV exports so that we can continue using them in the same way we did with Excel exports?