Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10167

Language pack crashes JIRA Agile Scrum board. [Transferred from GHS-10184]

      Enabling language pack crashes JIRA Agile Scrum board in Planning mode.
      https://support.atlassian.com/browse/GHS-10184

        1. issue2visible.png
          issue2visible.png
          58 kB
        2. JIRA Agile-6.3.3-language-pack-ko_KR.jar
          42 kB
        3. repeated.png
          repeated.png
          90 kB

            [JSWSERVER-10167] Language pack crashes JIRA Agile Scrum board. [Transferred from GHS-10184]

            2rf3r3232

            Narendar Sharma added a comment - 2rf3r3232

            I've fixed JIRA Agile's formatting code to be more tolerant of incorrect syntax. Rather than throwing an error, the formatting function will return empty output for keys which have incorrect syntax. In addition, a message will be output to the Javascript console, for example:

            Bad formatting of message: 0,choice,0#0 이슈|1#1 이슈|1<{0,number} 이슈
            

            Michael Tokar added a comment - I've fixed JIRA Agile's formatting code to be more tolerant of incorrect syntax. Rather than throwing an error, the formatting function will return empty output for keys which have incorrect syntax. In addition, a message will be output to the Javascript console, for example: Bad formatting of message: 0,choice,0#0 이슈|1#1 이슈|1<{0,number} 이슈

            Hello CJL,

            Thank you for investigation and fixing the translations.

            Let's keep this issue open so JIRA Agile folks can fix their javascript. Translation mistakes should not break the entire service.

            Cheers,
            Jacek

            Jacek Jaroczynski (Inactive) added a comment - Hello CJL, Thank you for investigation and fixing the translations. Let's keep this issue open so JIRA Agile folks can fix their javascript. Translation mistakes should not break the entire service. Cheers, Jacek


            As you can see above, I had to use exactly same word on each parameters.
            That's why I tried to bent the rule, but I won't do it again.

            I'm just saying that current JIRA Agile's client exception handler shows too less information to debug something such as this problem.

            Thank you .

            ChangJoon Lee added a comment - As you can see above, I had to use exactly same word on each parameters. That's why I tried to bent the rule, but I won't do it again. I'm just saying that current JIRA Agile's client exception handler shows too less information to debug something such as this problem. Thank you .

            I found few other items, and it is fixed.
            However, I want to share with you.

            My language does not care of plurals.
            So, I skipped

            {0,choice,0# issue|1#1 issue|1<{0,number} issues}
            

            into this

            {0,choice,0#|1#|1<} issues
            

            Then, it gave me the same error.

            ChangJoon Lee added a comment - I found few other items, and it is fixed. However, I want to share with you. My language does not care of plurals. So, I skipped {0,choice,0# issue|1#1 issue|1<{0,number} issues} into this {0,choice,0#|1#|1<} issues Then, it gave me the same error.

            Dear, Jacek,
            It seems like TRANS-858 caused this problem.

            As you can see, < is escaped.

            ChangJoon Lee added a comment - Dear, Jacek, It seems like TRANS-858 caused this problem. As you can see, < is escaped.

            Also, I found these problem not only Scrum, but Kanban too.
            http://(JIRA)/secure/RapidBoard.jspa?rapidView=6&view=reporting&chart=controlChart&swimlane=10&swimlane=11&column=21

            Control Chart in Report mode of Kanban generates exactly same error.

            ChangJoon Lee added a comment - Also, I found these problem not only Scrum, but Kanban too. http://(JIRA)/secure/RapidBoard.jspa?rapidView=6&view=reporting&chart=controlChart&swimlane=10&swimlane=11&column=21 Control Chart in Report mode of Kanban generates exactly same error.

            It seems to be JIRA Agile bug. It fails in case of some specific translations.

            Jacek Jaroczynski (Inactive) added a comment - It seems to be JIRA Agile bug. It fails in case of some specific translations.

              Unassigned Unassigned
              6e4387217e11 ChangJoon Lee
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: