Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-35589

CSV import does not handle French characters

XMLWordPrintable

      When creating an issue in JIRA, French characters will be rendered correctly but when the issue is created from CSV import, these characters will be rendered as �

      Steps to reproduce

      1. Create a CSV file that contains:
        • Summary: [Déclaration d'accident] - Impression à double
        • Description: La déclaration qui est émise par le programme de manière automatique lorsque l'accident est créé depuis une prestation sort deux fois à
      2. Now create a new issue in JIRA with the same information

      Results
      The issue created via CSV import will render special characters with �, while issue created in JIRA itself will render the characters properly.

            [JRASERVER-35589] CSV import does not handle French characters

            Chuyen HUYNH added a comment -

            Did anybody solve the issue for Vietnamese characters yet?

            Thanks

            Chuyen HUYNH added a comment - Did anybody solve the issue for Vietnamese characters yet? Thanks

            DaoL added a comment -

            I've used iso-8859-1 encoding but Vietnamese characters are incorrect font. What is encoding for Vietnamese character?

            DaoL added a comment - I've used iso-8859-1 encoding but Vietnamese characters are incorrect font. What is encoding for Vietnamese character?

            Oswaldo Hernandez (Inactive) added a comment -

            Consequently, the correct file encoding must be selected for the import to be successful.

            Oswaldo Hernandez (Inactive) added a comment - Consequently, the correct file encoding must be selected for the import to be successful.

            Oswaldo Hernandez (Inactive) added a comment -

            From the linked JIM-1081 issue:

            CSV Importer seems to be working fine when correct file encoding is filled on CSV Import page.

            CSV import page (Advanced) asks user to specify file encoding, by default it is set to 'UTF-8'. I've attached sample file - if you just import it without changing encoding - special characters are corrupted, but if you pick iso-8859-1 encoding everything seems to be imported correctly.

            Oswaldo Hernandez (Inactive) added a comment - From the linked JIM-1081 issue: CSV Importer seems to be working fine when correct file encoding is filled on CSV Import page. CSV import page (Advanced) asks user to specify file encoding, by default it is set to 'UTF-8'. I've attached sample file - if you just import it without changing encoding - special characters are corrupted, but if you pick iso-8859-1 encoding everything seems to be imported correctly.

            MattS added a comment -

            I agree, importing non-UTF 8 data is a painful experience.

            MattS added a comment - I agree, importing non-UTF 8 data is a painful experience.

            Andreas K. added a comment -

            Hello,
            It would be interesting to test the import not only with french characters but also German, Spanish and other languages supported by JIRA that contain non-English letters (e.g. ö, ä, ü, ç, é, è, à , etc.).

            This issue affects especially JIRA customers that would like to migrate their current issue/ticket base to JIRA, and if it is in a language that contains special character. In my case I am putting together a POC to go from HP QC to JIRA, but cannot finalize it because the data migration without the characters would be a show stopper.

            Hope you can find a solution
            Thx a lot & cheers!

            Andreas K. added a comment - Hello, It would be interesting to test the import not only with french characters but also German, Spanish and other languages supported by JIRA that contain non-English letters (e.g. ö, ä, ü, ç, é, è, à , etc.). This issue affects especially JIRA customers that would like to migrate their current issue/ticket base to JIRA, and if it is in a language that contains special character. In my case I am putting together a POC to go from HP QC to JIRA, but cannot finalize it because the data migration without the characters would be a show stopper. Hope you can find a solution Thx a lot & cheers!

              Unassigned Unassigned
              cchan Chung Park Chan
              Affected customers:
              1 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: