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

Non-latin characters are stripped in customfield name and request type

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Handled by Support
    • Icon: Low Low
    • None
    • 2.5.0
    • None

      Hello,

      we are using Jira 6.4.7 and 6.4.4 for our customers. Database is MsSql 2012 with CI_AI collation, but some fields in service desk are stripped from diacritics.

      Those fields are:

      • label for fields
      • request type name
        However, if you put these diacritis in name of the portal or description of portal everything works fine.

      Steps to reproduce:
      1) go to service desk settings
      2) change request name to "Nový servisní požadavek"
      3) the request name will be changed to "Novy servisní pozadavek"

      I have found ticket JSD-1419 yet I am unable to find clean solutin for this, should I change the field definition from varchar to nvarchar for tables StatusMapping and ViewportField? Is it safe to change the definition on database level?

      Can I get clean solution to this? I guess it is bug in Service desk because it works on portal name, but not for field names.

      Thanks for response.

          Form Name

            [JSDSERVER-2218] Non-latin characters are stripped in customfield name and request type

            Matthew McMahon (Inactive) added a comment -

            Hi karel.hala,

            Could you create a support ticket at https://support.atlassian.com in order to get some specific assistance with this issue? The credentials should be the same as for this site (https://jira.atlassian.com).

            However, yes, as you pointed out a possible workaround for now is mentioned at https://jira.atlassian.com/browse/JSD-1419?focusedCommentId=718779

            I am unable to provide any more details about this, but it seems to have helped that users instance. The real fix has been required in the underlying ActiveObjects dependency, which will be available with the next major JIRA release.

            For the next release, exporting data and reimporting into a new instance will be the recommended method.

            Thanks!
            Matt
            JIRA Service Desk Product Team

            Matthew McMahon (Inactive) added a comment - Hi karel.hala , Could you create a support ticket at https://support.atlassian.com in order to get some specific assistance with this issue? The credentials should be the same as for this site ( https://jira.atlassian.com ). However, yes, as you pointed out a possible workaround for now is mentioned at https://jira.atlassian.com/browse/JSD-1419?focusedCommentId=718779 I am unable to provide any more details about this, but it seems to have helped that users instance. The real fix has been required in the underlying ActiveObjects dependency, which will be available with the next major JIRA release. For the next release, exporting data and reimporting into a new instance will be the recommended method. Thanks! Matt JIRA Service Desk Product Team

              Unassigned Unassigned
              d6a4f343dab4 Karel Hala
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: