Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2912

Input field of some object doesn't support double byte characters

XMLWordPrintable

    • 5

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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. 

      1. Visit Enterprise > Goals
      2. 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.

      Screen Recording 2021-01-15 at 11.23.10.mov

        1. Screen Recording 2021-01-15 at 11.23.10.mov
          21.99 MB
        2. Screen Shot 2021-03-09 at 10.11.04.png
          Screen Shot 2021-03-09 at 10.11.04.png
          61 kB

            [JIRAALIGN-2912] Input field of some object doesn't support double byte characters

            backbone-sync-bot made changes -
            External issue URL New: https://softwareteams.atlassian.net/rest/api/2/issue/382140
            backbone-sync-bot made changes -
            Remote Link New: This issue links to "JAAND-159 (Software Teams JIRA)" [ 1030808 ]
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 5
            Masahito Sugahara made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 950676 ]
            Nobuyuki Mukai made changes -
            Description Original: h3. 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.

            (i) Check out the full report [here|https://hello.atlassian.net/wiki/spaces/JA/pages/998264795/Jira+Align+test+cases+for+Japanese]

            h3. Steps to Reproduce

            Here's an example of the "Enterprise > Goal" object. 
             # Visit Enterprise > Goals
             # Add some Goal objects with Japanese e.g. "テスト"

            h3. Expected Results

            Goals object is saved as the user's input. 
            h3. Actual Results

            The Japanese text is garbled.
            !Screen Shot 2021-03-09 at 10.11.04.png|width=383,height=150!
            h3. Workaround

            Change SQL Server's DB collation to the target language as [https://hello.atlassian.net/wiki/spaces/~nmukai/pages/812738693/Jira+Align+DBCS+support].
            (i) Please note this is only for the target language. For example, if you set DB collation to Japanese, you can use Japanese + English only. It doesn't mean DBCS + English i.e. Japanese collation still cannot accept Korean or Chinese at the same time. 

             

            As for the Workaround for the "{*}Setting > Access Control > People{*}" object, you can save DBCS by making an input twice after you filled fields.

            [^Screen Recording 2021-01-15 at 11.23.10.mov]             		New: h3. 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.

            (i) Check out the full report [here|https://hello.atlassian.net/wiki/spaces/JA/pages/998264795/Jira+Align+test+cases+for+Japanese]
            h3. Steps to Reproduce

            Here's an example of the "Enterprise > Goal" object. 
             # Visit Enterprise > Goals
             # Add some Goal objects with Japanese e.g. "テスト"

            h3. Expected Results

            Goals object is saved as the user's input. 
            h3. Actual Results

            The Japanese text is garbled.
            !Screen Shot 2021-03-09 at 10.11.04.png|width=383,height=150!
            h3. 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.

            [^Screen Recording 2021-01-15 at 11.23.10.mov]
            Sam Tsubota made changes -
            Link New: This issue is related to JIRAALIGN-5913 [ JIRAALIGN-5913 ]
            Don Fuller made changes -
            Resolution Original: Not a bug [ 12 ]
            Status Original: Closed [ 6 ] New: Future Consideration [ 11775 ]

            Matt McKinstry added a comment -

            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

            Matt McKinstry added a comment - 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

            Neill Walker added a comment -

            Thank you for the update. We have decided to halt our internal roll-out and cancel our license this year because double-byte characters are a base requirement here in Japan. This is an even bigger issue for most of our clients who have teams in Korea, China, and Vietnam, so we will hold off introducing Align until it is ready for the market. I hope it is part of your quarterly planning. 

            -Neill

            Neill Walker added a comment - Thank you for the update. We have decided to halt our internal roll-out and cancel our license this year because double-byte characters are a base requirement here in Japan. This is an even bigger issue for most of our clients who have teams in Korea, China, and Vietnam, so we will hold off introducing Align until it is ready for the market. I hope it is part of your quarterly planning.  -Neill
            Don Fuller made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

              kforeman@atlassian.com Kyle Foreman
              nmukai Nobuyuki Mukai
              Votes:
              9 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: