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

Unicode Characters in JSON Import Display Incorrectly

XMLWordPrintable

      Issue Summary

      When importing issues with the External System Import -> JSON importer, if any of the fields in the exported JSON file contain Unicode characters (like in the table below) they will not display property in some environments after successful import:

      Unicode code point UTF-8 (dec.) name
      U+2018 226 128 152 LEFT SINGLE QUOTATION MARK
      U+2019 226 128 153 RIGHT SINGLE QUOTATION MARK

      Steps to Reproduce

      1. Copy the JSON attached in the next internal update
      2. Change the following items:
        • Project key (must be an existing project on JIRA instance)
        • Status (must be valid for issue type)
        • Reporter/Assignee (for ease of permissions to access)
      3. Import the file using the External System Import -> JSON option

      Expected Results

      In a few instances, the characters show up correctly in the Summary and Description fields:
      MySQL 5.7.19 - JIRA 7.12.3
      MSSQL 2017 - JIRA 7.12.3
      postgres 9.5 on 8.1
      postgres 9.5 on 7.8.1

      Actual Results

      Most of the time, the characters show up incorrectly. This has been reproduced in:
      PostgreSQL 9.3 - JIRA 7.8.0
      PostgreSQL 9.3 - JIRA 7.12.3
      MSSQL 2012 on 7.8.1
      MSSQL 2014 on 7.8.1
      MSSQL 2016 on 7.9.2

      When looking at the value in the jiraissue table -> summary or description fields, the characters are stored incorrectly in the database. It would appear that the problem is either in the JSON importer or perhaps with some of the specific database versions where the behavior is exhibited.

      Workaround

      Replace unicode characters with non-unicode characters where possible

              Unassigned Unassigned
              asweeten ASweeten (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: