-
Bug
-
Resolution: Tracked Elsewhere
-
Low (View bug fix roadmap)
-
None
-
None
-
Severity 3 - Minor
-
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.
- duplicates
-
BSERV-4584 create branch from issue - chars replacing missing "Ł" char
-
- Closed
-
- is caused by
-
BSERV-4945 Stash create branch page unable to use Japanese, Korean and other non-ASCII characters from JIRA link in the branch name
-
- Closed
-
- was cloned as
-
FUSE-1438 Failed to load
Form Name |
---|
[JSWSERVER-14918] Unable to create Stash branch names containing Japanese, Korean or non-ASCII characters from development panel
Workflow | Original: JAC Bug Workflow v2 [ 2854091 ] | New: JAC Bug Workflow v3 [ 2938269 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542792 ] | New: JAC Bug Workflow v2 [ 2854091 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1527168 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542792 ] |
Component/s | New: Development Panel [ 43313 ] | |
Component/s | Original: Issue - Development Panel [ 25405 ] | |
Key |
Original:
|
New:
|
Symptom Severity | New: Minor [ 14432 ] | |
Affects Version/s | Original: 6.2.7 [ 42190 ] | |
Project | Original: JIRA (including JIRA Core) [ 10240 ] | New: JIRA Software (including JIRA Agile) [ 12200 ] |
Labels | Original: i18n warranty | New: i18n jira-development-panel warranty |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 698583 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1527168 ] |
Component/s | Original: Internationalisation [ 10290 ] | |
Labels | Original: warranty | New: i18n warranty |
Resolution | New: Tracked Elsewhere [ 15 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
This is a purely Stash issue, not fusion related. Fusion passes the JIRA summary through to stash, which then processes it.