-
Bug
-
Resolution: Fixed
-
High
-
17
-
Severity 3 - Minor
-
12
-
Problem
When viewing the exported CSV file in Excel, the special characters aren't rendered correctly.
Steps to Replicate
- Create an issue with special characters
- Go to Issue Navigator and click Export > Current fields
- Open the exported CSV in Excel
Expected Behaviour
The special characters are displayed properly.
Actual Behaviour
Special characters are not correctly rendered. As an example, "phố xưa" is displayed as "phố xÆ°a" when viewed in Excel.
Workaround
Option 1:
- Open the file with Notepad
- Choose File > Save as
- File name: jira.csv (any name but must end with .csv)
- Save as type: All files
- Encoding" UTF-8
Option 2:
- Open the exported CSV file with Notepad++
- Under "Encoding", it should be shown File is UTF-8 without BOM.
- Converting the file to UTF-8 with BOM will allow the file to be displayed correctly in Excel.
Note:
Viewing the CSV in text editor works fine.
- is cloned from
-
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-77924] Special Characters Exported via CSV not Rendered Correctly in Excel
Hi Jordan, do you know if it is planned to fix this bug in server/DC versions too ?
Hi all,
We've begun rolling out a fix for this bug - 100% of customers will receive this update by early next week.
Export Excel CSV now works with special characters (including characters for languages other than English). We have also added a new export option, Export CSV, which retains the past functionality of 'export Excel CSV' to avoid breaking changes when exporting .csv to products other than Excel.
Please reach out to me if there are any concerns.
Jordan
I've just started using Jira, and it's disappointing to see anoying little bugs like this that are so frustrating. I look forward to seeing this fixed, but based on the length of time it's been hanging around, I'm not sure when that will be.
Still an issue with exports. Must open/save the file to UTF-8 as work around. Can also open the file in excel using the data menu, from text/csv, with file origin 65001: Unicode (UTF-8) and clicking the load button as mentioned in this knowledge article - https://confluence.atlassian.com/jirakb/exported-csv-does-not-display-properly-in-excel-that-contains-non-english-characters-874626219.html
I have a regular export that is client facing and from what I can tell the Apostrophe, Open & Close Quotes, and a space after the last period renders some version of "â€". How has this been known for this long and it is still a THING?
Hi, we need to be able to Export CSV and import back to Jira without losing any words/characters/ meaning...
guys. i am in the middle of a hughe migration project to jra service desk and a simple thing like adding the right BOM is open since one year???
you need instructions how to change (and for gods sake it is a silly small thing) go to Atlassian ticket JST-496060.
Please act here!
I understand that there is still no solution. Why do I need this feature if it does not work? Can I immediately insert a link to the marketplace in the product menu?! 
Hey bd164ec66a4d
Unfortunately the fix being rolled out is only targeting Jira Cloud
I'd recommend Watching and clicking "This affects my team" on the Jira Server ticket to help the owning team prioritise it