nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA 7.2.x Excel export gone?

Michael Kolb1

With my old JIRA Version there was an option to export an issue list to an excel file. I've updated to JIRA 7.2.x - the option is not available anymore (only export to Word is left). Unfortunately CSV is not an option, as Excel is unable to correctly import fields that contain the text-delimiter.

How to re-enable Excel export?

Accepted answers

Marc_Teufel_hama_de

You can activate Excel in your jira-config.properties with following line:

jira.export.excel.enabled=true

(This works vor JIRA Core 7.2.2 and 7.2.3)

Alternatively you can set your Region to US and configure the list separator to comma. Then Excel export/import in Excel will work again.

Alternative 2: Save the csv file and add "sep=," as the first line in the file. When opening the file in excel the comma will be used as a delimiter

All comments

Nic Brough -Adaptavist-

It's not a case of enabling it, it has gone.

Excel should have no problem reading CSV though. Is there a setting in Excel that's breaking it?

Michael Kolb1

The problem is simple to reproduce: Create an issue with the description 'this is a text containing a "text-delimiter"', and export it (including the field "description") to CSV. The CSV will contain '"this is a text containing a ""text-delimiter"""', which destroys the whole column layout in excel, as the escaped text-delimiter is not recognised.

Denis Boisvert_m3sw0g

It should work. You might have the following issue that I had myself not too long ago:

http://stackoverflow.com/questions/2668678/importing-csv-with-line-breaks-in-excel-2007

Aron Gombas _Midori_

If CSV does not work for you (or you're looking for something more powerful), the Better Excel Plugin can export actual XLSX files for you.

Ben Middleton

There are other issues with the new CSV export. For example, if your field includes commas, you can no longer export sensibly. There's a bug for this:

https://jira.atlassian.com/browse/JRA-62517

Ben Middleton

Thanks - this looks interesting. However, we were using the previous bundled functionality successfully. Atlassian should not be removing functionality which requires customers to have to invest in 3rd party solutions.

Valentijn Scholten

Another way in which functionality is reduced with the CSV export is that it no longer exports a direct link (URL) to the issue in JIRA. The prevouis Excel export had this, very conventient for people receiving an Excel sheet and wanting to look at the issue details.

Marc_Teufel_hama_de

You can activate Excel in your jira-config.properties with following line:

jira.export.excel.enabled=true

(This works vor JIRA Core 7.2.2 and 7.2.3)

Alternatively you can set your Region to US and configure the list separator to comma. Then Excel export/import in Excel will work again.

Alternative 2: Save the csv file and add "sep=," as the first line in the file. When opening the file in excel the comma will be used as a delimiter

Kai Gottschalk_l6llgz

Hi Marc,

many thanks for this workaround. I tried it with JIRA 7.2.2 in JIRA SW including a restart unfortunately without any success. Are there any other known pitfalls/things to consider (deletion of caches, etc.), which might help to get this running again.

Cheers
Kai

PS: Another restart helped the export-functionality do re-appear. Thanks for this hint!

B_ Normann P_ Nielsen

Works fine in JIRA Software v7.2.3

Borut Hadžialić

Works in JIRA 7.2.2 SW for me.

Tayyab Bashir

This is a nice plugin.
Are there any other plugins that provide the export functionality for Excel but a little expensive?

Dan_0wy0t6

You might be interested in the Exporter Issue Comments for CSV and Excel - cheaper but still has the now gone Export to Excel functionality.

Deepali Bagul

Thanks @Nic Brough [Adaptavist],

I was looking at wrong place. I added the jira-config.properties to the root of your JIRA home directory (var/atlassian/application-data/jira/) and added the line jira.export.excel.enabled=true and restart the JIRA server.

I got it working correctly for JIRA 7.2.3 , Thanks !

Mark Biro

Hi there,

With ImpEx you can import and export your issues to XLSX or HTML (even with comments, images and attachments)!

Feel free to give it a try: https://marketplace.atlassian.com/plugins/com.moresimp.impex/server/overview

Best regards, Mark

QDappnet

Same here, thanks for the home directory path info.

I created jira-config.properties file (with a text line jira.export.excel.enabled=true), but saved to wrong location /opt/atlassian/jira/

After correct saving the properties file to /var/atlassian/application-data/jira/, I restarted JIRA, there are 2 new options added to Export: Excel (All fields) and Excel (Current fields)

I have JIRA v7.4.3

JIRA application home directory
https://confluence.atlassian.com/adminjiraserver073/jira-application-home-directory-861253888.html

Teja

Thanks guys, It worked.

Gezim Shehu [Communardo]

Still working in JIRA 7.3

1. Stop JIRA.
2. Locate the jira-config.properties file in the $JIRA_HOME directory. If the file does not exist, please proceed to create it.
3. Open the file and add the below on a separate line:

jira.export.excel.enabled=true

4. Save this file.
5. Restart JIRA.

Sean Kronberg

works in 7.5.0, as well.

Gairat Rakhimbaev

configuration file workaround works in 7.5.0

thanks much!

Marc Demhartner

We´re using Jira 7.6.0 - with Excel 2016 i am getting an error when trying to open the exported excel file. Excel basiclly says, that the file format is not correct. I can open it after i press Yes, but it looks "broken" - Any1 else has this problem?

Michael Kornatzki

As far as i know jira never exports an excel-file.

It was only a menu item named "Excel" but it was a html-file with an extension xls.

Therefore now the menu export-HTML is better.

If you look into the "xls" file with an editor you will see html (also in old files).

Gezim Shehu [Communardo]

Michael is correct (Y)

Aron Gombas _Midori_

Yes.

Jira exports HTML files with the .xls file extension and Excel finds them suspicious. It has always been working like this.

Please read this question from the top, there are multiple things you can do.

jobinjames

works. Thanks

Solomon Vansteenburg

I hate to rise the dead on this thread, but I seem to be in a pickle. I HAD this issue, solved it due to this thread, and now have the same issue again even though the fix is still in place. I upgraded to 7.3.7 back in June of last year and haven't applied any updates since. We were able to export to Excel for a good long while, but suddenly in the past month or so I've been getting reports from the users that they can't do it anymore. Why?

Nic Brough -Adaptavist-

It can't just change like that. You (as in your organisation, not just you) have removed or changed the flag from the properties file and restarted Jira

Solomon Vansteenburg

I'm (supposed to be) the only one who has access, let alone knows anything about me doing it. The setting is still there in the properties file, and the file hasn't been modified since 8/10/2017 when I made the original change. There are a few people who have heightened privileges inside of JIRA. Could it have been meddled with inside of JIRA?

Nic Brough -Adaptavist-

It might be possible to kill it with a property in global configuration -> advanced, or with javascript hacks. Is the properties file still fully read/write by the jira user?

I can't think of other ways to remove it.

SIGERI

Si funciona,

Yo estoy in Linux y seguí las instrucciones de Quy Duong,

Saludos,

Ananías

AMIT GULATI

We are recently migrated to JIRA 7.2 and faced the same challenge. Here are two ways in which we have been able to workaround:

1. Using Pivot Table and Pivot Chart gadgets in confluence, we are able to create pivot charts on realtime data.

2. Instead of using export to csv, I have used export to printable, copy all and paste in excel. Although this approach requires little cleanup but it ensures that required fields are in the right format in excel.

In my view, export to excel must be avoided as much as possible because that leads us away from using live dashboards and set wrong expectations with stakeholders.

Nic Brough -Adaptavist-

I agree - I don't like export to a spreadsheet because it implies the user is going to try to do "clever" reporting.

I was on a project at a major financial company many years ago where there were a lot of spreadsheets floating around. We were increasingly having problems where people would use the reports in a system and get a true representation of what was in there, and then seeing people export to a spreadsheet, do "clever" reporting, and start arguments in meetings because their report didn't tell the same story as the one in the system.

We did a project that took a selection of spreadsheets and went into detail about how accurate they were. The numbers that stick in my mind were that the reports coming out of 30% of them were, quite simply, wrong. But that was only for simple exports by a single user. When they were shared and edited by 2 people, the failure rate jumped to over 80% and 3 or more people gave us a 98%.

To be fair, these were not simple spreadsheets where someone has got a couple of hundred lines and generated a simple graph. All of them had at least one calculation or formula, and at least a thousand lines.

But, I stand by it. Extracts are mostly useless. A data extract, manipulation and report should always be questioned as to its accuracy. And its timing, as a lot of people fail to grasp that exports are point-in-time, and obsolete seconds after being done.

Rafal Sojka

We don't have impact on people who tweak their data but the functionality of application should not be limited due to such reason. Excel is and will be a standard tool in many businesses and unfortunately not all people are so technically savvy they know what CSV is and know how to deal with it. Finally, we had to enable the export to Excel by setting the jira.export.excel.enabled variable to true.

Nic Brough -Adaptavist-

Excel and other spreadsheets should be banned, not seen as a "standard tool". As I described earlier, most spreadsheets are simply wrong when they're used for reporting.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core