Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-12148

When using Japanese as the profile language and more than one pull request is linked to a commit, the commit details don't load correctly

    XMLWordPrintable

    Details

      Description

      Issue Summary

      The commit details, including the linked pull requests, Jira issues, build status, tags, watch option don't load when Japanese is set as the profile language and more than one pull request is linked to the commit.

      Steps to Reproduce

      Prerequisites
      Have a commit linked to more than a pull request. This can be done, for example, following these steps:

      • Create a new branch
      • Push a change
      • Create a pull request
      • Decline the pull request
      • Create a new pull request from the same source branch
      • Browse to the commit page (<Bitbucket URL>/projects/<project>/repos/<repository>/commits/<commit hash>)

      Expected Results

      The commit details are correctly displayed as they are in the other languages.

      This is the commit when using English as the profile language:

      Actual Results

      Only the commit id is displayed, no other details are shown when switching the profile language to Japanese:

      The browser console output contains the following error:

      Uncaught TypeError: Cannot read property '1' of null
          at g (format.js?_statichash=70bf83a15ed6cbf89aee424732dc6d07-CDN%2F-74168433%2Fe54d6da%2F1%2F951013b189528205e25558416ad0761d&locale=ja-JP:1)
          at b (format.js?_statichash=70bf83a15ed6cbf89aee424732dc6d07-CDN%2F-74168433%2Fe54d6da%2F1%2F951013b189528205e25558416ad0761d&locale=ja-JP:1)
          at Object.a [as format] (format.js?_statichash=70bf83a15ed6cbf89aee424732dc6d07-CDN%2F-74168433%2Fe54d6da%2F1%2F951013b189528205e25558416ad0761d&locale=ja-JP:1)
          at bitbucket.internal.feature.commit.commitPullRequests.commitPullRequests.summaryPanel (commit-pull-requests.soy.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:17)
          at Object.h [as _getValue] (web-fragment-manager.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:2)
          at view (descriptor.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:1)
          at h (web-fragment-manager.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:2)
          at p (web-fragment-manager.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:3)
          at web-fragment-manager.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:3
          at Object.getWebPanels (web-fragment-manager.js?_statichash=0ee68725041d1f6b2343867428213903-CDN%2F-74168433%2Fe54d6da%2F1%2Faf6f795a1275f986a428b8f68fba707a&locale=ja-JP:7)
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              fdoherty@atlassian.com Frank Doherty
              Reporter:
              ccurti Caterina Curti (Kate)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: