You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
From any session or accounts, after exporting and creating the xls file from a filter, MS-Excel is not able to open the file. The file looks well created with normal size, however the sheet can not be loaded by the excel application.
Few days ago, the function was working fine.
Thx for your support.
See if you have installed the following Excel updates. I noticed this problem right after these were installed and it no longer occurs for me after they were removed.
Those who'd prefer an actual solution where you can keep exports secure without turning off security checks in Excel, should check out the Better Excel add-on.
In a nutshell: it exports real XLSX files, therefore Excel "opens these in a secure way" (plus offers a lot of advantages in comparison to the files created by the built-in Excel export feature).
Is this for Cloud or Server?
Have you created or changed the configuration of any custom fields that are being exported? Can you try an "export only current fields" on a really simple issue navigator showing maybe just key, summary and description?
Can you open the .xls in a text editor and check that it looks valid in there? (it's not actually an excel file, it's xml that says "I'm a spreadsheet" so that any spreadsheet can open it if it understands xml)
Ok, does the xml look valid in there? Any odd characters? Check it with some form of xml validation tool?
That looks fine to me, and I can open it directly in Excel in a couple of seconds (three lines of issues right?). I am on a Mac, but with Office installed.
If it's not working for you then I suspect you may have an issue with your Excel install, rather than JIRA