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?
You can activate Excel in your jira-config.properties with following line:
(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
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.
PS: Another restart helped the export-functionality do re-appear. Thanks for this hint!
would you kindly tell me the path of the properties file?
Inside my JIRA installation there is no jira-config.properties file. I'm using JIRA Software version 7.2.6.
I found $JIRA_HOME/atlassian-jira/WEB-INF/classes/jira-features.properties which had the option jira.export.csv.enabled=true, so I placed inside that file the option you suggested, but while watching catalina.out during startup I found this:
jira.export.excel.enabled : false
Thanks in advance for your help!
No, it's not officially supported, because they've turned it off by default.
Turning it on will do no harm though - worst case is that enables a broken version of the exports, but that won't do anything worse than not work well and produce rubbish downloads. If they remove the code, then the property will simply be ignored.
Hi @Nic Brough [Adaptavist]
Inside my JIRA home directory $JIRA_HOME/atlassian-jira/WEB-INF/classes/ their was no jira-config.properties file. As per the docs i created jira-config.properties file and added the line jira.export.excel.enabled=true and restart the JIRA server. but this doesn't work for me on our JIRA 7.2.3
Thanks in advance for your help!
I'm noticing in the CSV export, if an issue has more than one component, label, etc, it creates a new column rather than prior to 7.2 and using the Excel export, it would concatenate the values in one column. Is there a setting where I can turn off the "create column for each value"?
Guys, i am facing issue in Jira software 7.3.5
As mentioned in the comments i have created a file "jira-config.properties " in location "$JIRA_HOME/atlassian-jira/WEB-INF/classes/" then added the line "jira.export.excel.enabled=true" in the fiile and restarted the server but still its not working.
In the jira screen in Export section i am not finding any option called excel.
Please can anyone help me on this.
Thank you in advance.
@nic brough , I am tring to expoet from issue navigator only.
I have issue filter which i am trying to export but i am getting to export it in csv, printable, xml, RSS and word.
But i am not finding the export in excel format, which we had in the previous version jira.
Thank you in anticipation
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.
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.
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 !
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
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.
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.
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.
Spreadsheets - helping people misrepresent their data and giving them inaccurate reports since 1976
There is not one place I've seen use a shared spreadsheet well. One big place (financial) did an analysis of over 1,000 random spreadsheets and found that when a sheet had two people using it, there was an 80% chance of it being wrong. That jumped to 95% when three people were using it, and 100% when there were more than 3.
Just because something is old or well used, does not mean it is any good.
You're right if you are talking about people putting incorrect data in, but that's not what I meant by "misrepresentation". I was meaning that even given the correct data, people manipulate it to give calculations, diagrams and reports that are simply wrong.
Jira (and any other application designed for handling the raw data) will generally not allow people to do that. They give outputs that do represent the information correctly
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
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?
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?
Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events