-
Suggestion
-
Resolution: Unresolved
-
5
-
Issue Summary
Some object in Jira Align doesn't store double byte characters properly.
As far as I confirmed following objects are affected.
- Setting > Access Control > People
- Enterprise > Goal
- Enterprise > Brainstorming
- Enterprise > Agile Assessment
It looks like a people's name and most objects in Enterprise level is affected.
Check out the full report here
Steps to Reproduce
Here's an example of the "Enterprise > Goal" object.
- Visit Enterprise > Goals
- Add some Goal objects with Japanese e.g. "テスト"
Expected Results
Goals object is saved as the user's input.
Actual Results
The Japanese text is garbled.
Workaround
As for the Workaround for the "Setting > Access Control > People" object, you can save DBCS by making an input twice after you filled fields.
- is related to
-
JIRAALIGN-2938 Input field of some object doesn't support surrogate pair characters (e.g. emoji)
-
- Closed
-
-
JIRAALIGN-5913 Enterprise Insights: Support/Render double-byte character
- Not Being Considered
- is blocked by
-
JALPM-1189 You do not have permission to view this issue
- is connected to
-
JAAND-159 Failed to load
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ALIGNSP-11775 Loading...
All,
Thank you for your assistance with the double-byte character issue.
In Japan, this issue will be a roadblock to implementation (and sales).
We have a Tokyo-based client (financial services) who adopted Jira Align last year, but has struggled to implement and integrate due to lack of Japanese language support. The problem is not just data entry fields, but the entire UI/UX needs to be in Japanese (many of our potential Clients users - both at the Team and Executive-level - will not engage in English).
Japanese use four alphabets interchangeably: Kanji (Chinese characters), Katakana, Hiragana, and Latin. It's very common for sentences to contain all four character types.
We have another Client (Retail Goods) that adopted JSM, but have limited adoption rates for this same issue.
Our Japanese Clients will use locally developed project management software (e.g., JP1, DIVA, etc.) - that they openly recognize have inferior functionality and UX - on the sole rationale that its in Japanese and does not make their users uncomfortable. This is what's happening with the JSM example - the Client remains "stuck" on JP1 and DIVA.
Happy to provide additional context and local atmospherics
Cheers,
Matt