Russian characters not stored correctly in SQL Server on GreenHopper

XMLWordPrintable

    • Type: Bug
    • Resolution: Tracked Elsewhere
    • Priority: Medium
    • None
    • Affects Version/s: 6.1.3.2, 6.7.11
    • Component/s: None
    • 6.01

      When using SQL Server, unicode text (eg. Russian/Cyrillic) is not stored correctly in GreenHopper tables in the database. Characters are replaced with ?'s. The screenshot is on a vanilla instance with GreenHopper 6.1.3.2 installed. The issue seems to appears in Sprint (the name will change only after sprint started), Quickfilter, and Scrum.

      The following is the screenshot obtain from SQL Server database

      This issue seems to be similar to the bug reported in JRA-9154 on earlier version of JIRA. Where the issue relates to the field type where instead of VARCHAR is should be NVARCHAR

      Additional Info: This works correctly in Classic Board, but not Rapid Board.

        1. sql_collation.PNG
          56 kB
          Zul NS [Atlassian]
        2. sql_collation1.png
          16 kB
          Zul NS [Atlassian]
        3. sql_collation2.jpg
          131 kB
          Zul NS [Atlassian]

            Assignee:
            Unassigned
            Reporter:
            Zul NS [Atlassian] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: