Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-14918

Unable to create Stash branch names containing Japanese, Korean or non-ASCII characters from development panel

XMLWordPrintable

      If the JIRA issue summary contains non-ASCII characters – Japanese, Korean or even umlaut, then on creating a Stash branch from the development panel, the Stash UI will remove the non-ASCII characters from the proposed branch name.

      Environment

      JIRA 6.2.7
      Stash 3.1.1
      Browsers Chrome, Firefox

      How to reproduce

      • JIRA is integrated with Stash using Application Links
      • Create a JIRA issue with the summary in Japanese, Korean or having non-ASCII characters like umlaut
      • From JIRA Development Panel, click on 'Create branch'
      • In the Stash create branch screen, the suggested branch name will not contain any of the non-ASCII characters.

      Diagnosis

      • The Stash URL contains the proper JIRA summary including all characters, but Stash is not able to process the characters (similar to STASH-396). This is still being raised as a JIRA bug, because the error is observed from JIRA.

      Workaround

      • In the Stash Create Branch screen, copy-paste the JIRA summary as required and then the branch will be created correctly.

            [JSWCLOUD-14918] Unable to create Stash branch names containing Japanese, Korean or non-ASCII characters from development panel

            mwatson added a comment -

            This is a purely Stash issue, not fusion related. Fusion passes the JIRA summary through to stash, which then processes it.

            mwatson added a comment - This is a purely Stash issue, not fusion related. Fusion passes the JIRA summary through to stash, which then processes it.

              Unassigned Unassigned
              bjaison BejoyA
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: