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

'Edit Form' doesn't work when using Russian language

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • None
    • None
    • None
    • None

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary of Bug

      In the customer portal of Service Desk, if the issue type as well as the description is in Russian, the 'Edit Form' link will keep loading indefinitely

      Steps to Reproduce

      1. Create an Issue Type in Russian
      2. At the 'Customer Portal' portion of the Service Desk, create a new request type with the Russian issue type, and also use Russian text for the description
      3. Click on the 'Edit Form' link

      Additional Info

      • This seems to affect special characters. In addition to Russian, this was also reproducible when tested with Japanese
      • On the other hand, testing with Italian did not reproduce the behaviour

        1. servicedesk1.png
          servicedesk1.png
          3 kB

            [JSDSERVER-67] 'Edit Form' doesn't work when using Russian language

            Joshua Hansen added a comment - - edited

            Until the next release, you can work around this bug by using only English characters in the name when you first create the request type. After creation, you can change the name to whatever you want and the problem won't occur.

            Joshua Hansen added a comment - - edited Until the next release, you can work around this bug by using only English characters in the name when you first create the request type. After creation, you can change the name to whatever you want and the problem won't occur.

            Gilmore Davidson (Inactive) added a comment -

            This is caused by a bug when handling certain character sets in one part of the product, which we're tracking at JSD-5.

            This will be fixed in our next release.

            Gilmore Davidson (Inactive) added a comment - This is caused by a bug when handling certain character sets in one part of the product, which we're tracking at JSD-5 . This will be fixed in our next release.

              jpendleton Justus Pendleton (Inactive)
              jtye Joe Wai Tye (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: