Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8406

UTF-8 encoding does not work as expected for special characters while exporting the objects.

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • None
    • 4.16.0
    • None

      Issue Summary

      UTF-8 encoding does not work as expected for Spanish words while exporting the objects.

      Affected Version : 8.7.10

      Steps to Reproduce

      1. Create an object schema with few objects.
      2. Create an attribute with text type.
      3. Put a value for the text type attribute with some Spanish words like información.
      4. View the object. It will display the correct value as below 
      5. Export the objects with the following settings in a CSV:

      Expected Results

      All the "Spanish" words should be displayed correctly.

      Actual Results

      The CSV results show the weird characters as below:

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. export.jpg
          export.jpg
          143 kB
        2. image-2021-09-03-14-56-44-223.png
          image-2021-09-03-14-56-44-223.png
          177 kB
        3. image-2021-09-03-14-57-41-437.png
          image-2021-09-03-14-57-41-437.png
          180 kB
        4. Insight_-_Jira.jpg
          Insight_-_Jira.jpg
          109 kB
        5. Insight_-_Jira-1.jpg
          Insight_-_Jira-1.jpg
          72 kB
        6. reproducible in Excel.png
          reproducible in Excel.png
          78 kB
        7. screenshot-1.png
          screenshot-1.png
          171 kB

          Form Name

            [JSDSERVER-8406] UTF-8 encoding does not work as expected for special characters while exporting the objects.

            Jean-Baptiste Prat-Espouey made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Jean-Baptiste Prat-Espouey added a comment - https://jira.atlassian.com/browse/JSDSERVER-7177
            Kunal Kanojia made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Sam Nazha (Inactive) made changes -
            Link New: This issue relates to JSDSERVER-8392 [ JSDSERVER-8392 ]
            Steven de Groot made changes -
            Summary Original: UTF-8 encoding does not work as expected for Spanish words while exporting the objects. New: UTF-8 encoding does not work as expected for special characters while exporting the objects.

            Yinon Negev added a comment - - edited

            Tested this issue with various languages, exported from both Schema > Object Type View and the Insight Object Search - all giving the exact same results:

            LibreOffice, Numbers, Google Spreadsheet - shows all languages as expected.

            Excel on prem as well as Office 365 Live - does not show Special Characters, from different Languages when uploading the exported CSV.

            Yinon Negev added a comment - - edited Tested this issue with various languages , exported from both Schema > Object Type View and the Insight Object Search - all giving the exact same results: LibreOffice, Numbers, Google Spreadsheet - shows all languages as expected. Excel on prem as well as Office 365 Live - does not show Special Characters, from different Languages when uploading the exported CSV.
            Yinon Negev made changes -
            Attachment New: screenshot-1.png [ 411558 ]
            Yinon Negev made changes -
            Attachment Original: Testing multiple languages.png [ 411557 ]
            Yinon Negev made changes -
            Attachment New: Testing multiple languages.png [ 411557 ]

            Marina Veselić added a comment - - edited

            Additionally, exporting to any encoding results in the same error. In the version of Insight 8.6.8 the scenario was as follows: 

            1. Export objects.
            2. Select encoding Windows - 1250 or1252.
            3. Save the csv file.
            4. Double click on the file.
            5. All the characters were correctly represented when the file was opened in Excel.

            Since version 8.7.10 (maybe before) this does not work. Excel did not change. 

             

            Marina Veselić added a comment - - edited Additionally, exporting to any encoding results in the same error. In the version of Insight 8.6.8 the scenario was as follows:  Export objects. Select encoding Windows - 1250 or1252. Save the csv file. Double click on the file. All the characters were correctly represented when the file was opened in Excel. Since version 8.7.10 (maybe before) this does not work. Excel did not change.   

              a96407187058 Jean-Baptiste Prat-Espouey
              kmehta Krina
              Affected customers:
              4 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: