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

Referring to lines in comments



    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      Atlassian status as of March 2020

      Hi all,

      I'm excited to share that in Bitbucket Server 7.0 we shipped redesigned and optimised pull request page with several improvements you’ve been asking us, including support for linking directly to lines in the diff from comments.
      You can now click on the line number in the gutter to deep link to that line, similarly you can right click and copy the link from the line number and paste it into a comment, where it will be automatically formatted when rendering the comment. The link will be in the form of #filePath/filename?f=123 for the "from" side of the diff (context and removed lines) and #filePath/filename?t=123 for the the "to" side of the diff (added lines)

      You can find more information in the Bitbucket Server 7.0 release notes and Pull Requests documentation.

      Please, don't hesitate to leave feedback on the feature in the comments. This will help us to priorities further development.

      Michael McGlynn
      Bitbucket Server Developer

      Sometimes I want to refer to another line or function in a comment I’m making on a commit or PR. It’d be great if Stash added some way to generate a link to another line (or even a function, by name) inside of the Markdown syntax for comments.

      Perhaps something like:

      See #345old.

      Where `old` is used to designate the line relative to the file that’s being patched, and `new` would refer to the line relative to the file as it would be after the diff is applied.


        1. screenshot-1.png
          129 kB
        2. screenshot-2.png
          110 kB

        Issue Links



              Unassigned Unassigned
              4c762d6af390 Corey Steele
              6 Vote for this issue
              6 Start watching this issue