Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8766

Mouse over submodule commit link in source view throws incorrect "Page not found" error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • 4.6.1
    • 4.6.0
    • Repository - Source / Diff
      • Create a pull request with new commits from a fork to the parent repo.
      • Hover over a commit hash link for one of the commits originating in the fork.

      For pull requests coming from a different repo (fork) than the destination repo, hovering over the link to the commit hash causes a "Page not found" popup (see attached). It appears to be looking for the commit hash in the current repository instead of the submodule repository. Probably related to the new commit message preview feature.

          Form Name

            [BSERV-8766] Mouse over submodule commit link in source view throws incorrect "Page not found" error

            Owen made changes -
            Workflow Original: Stash Workflow - Restricted [ 1447511 ] New: JAC Bug Workflow v3 [ 3136258 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 1399716 ] New: Stash Workflow - Restricted [ 1447511 ]
            Michael McGlynn (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Michael McGlynn (Inactive) made changes -
            Link New: This issue duplicates BSERV-8708 [ BSERV-8708 ]

            Michael McGlynn (Inactive) added a comment -

            jan.magnusson This is also fixed as part of fixing BSERV-8708 in 4.6.1.

            Michael McGlynn (Inactive) added a comment - jan.magnusson This is also fixed as part of fixing BSERV-8708 in 4.6.1.
            Jan Magnusson made changes -
            Environment Original: * Browse to a repository that includes submodules
            * Hover over the commit hash link for one of the submodules             		New: * Create a pull request with new commits from a fork to the parent repo.
            * Hover over a commit hash link for one of the commits originating in the fork.
            Jan Magnusson made changes -
            Security Original: Reporter and Atlassian Staff [ 10751 ]

            Jan Magnusson added a comment -

            We have not yet been able to install 4.6.1 to see if this is resolved by the fix bor BSERV-8708, but the same behavior is visible when looking at pull requests where the originating repo is different from the destination. Have you in any way verified this case in conjunction with making the fix?

            Jan Magnusson added a comment - We have not yet been able to install 4.6.1 to see if this is resolved by the fix bor BSERV-8708 , but the same behavior is visible when looking at pull requests where the originating repo is different from the destination. Have you in any way verified this case in conjunction with making the fix?
            Jan Magnusson made changes -
            Description Original: For repositories that have submodules, hovering over the link to the commit hash causes a "Page not found" popup (see attached). It appears to be looking for the commit hash in the current repository instead of the submodule repository. Probably related to the new commit message preview feature. New: For pull requests coming from a different repo (fork) than the destination repo, hovering over the link to the commit hash causes a "Page not found" popup (see attached). It appears to be looking for the commit hash in the current repository instead of the submodule repository. Probably related to the new commit message preview feature.
            Jan Magnusson made changes -
            Link New: This issue is cloned from BSERV-8708 [ BSERV-8708 ]

              mmcglynn Michael McGlynn (Inactive)
              7a8a8dc21e7e Jan Magnusson
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: