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

Pull Request Multiline Comments

XMLWordPrintable

    • 317
    • 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 July 2024

      Hi everyone,

      Thank you for taking the time to vote and comment on this suggestion. Your feedback has helped us gain a better understanding of how this impacts you and what you're aiming to accomplish with Bitbucket Data Center. We are delighted to share that this suggestion has been prioritised, and our team is working on it as we speak. We have also committed to a target release quarter as part of our roadmap. For the latest information on when to anticipate the release, please visit our roadmap.

      We appreciate your patience and are excited to release this for you soon. You can learn more about our prioritization process here.

      Cheers,

      Vicky Hu

      Product Manager - Bitbucket Data Center

      Original request description

      This is a follow up to issue STASH-3314 that was closed. In that issue Jens Schumacher said that the reason why multiline comments were not added is because in Crucible it was very hard to select actual code, with what I agree, but I would like to suggest an improvement.

      Why not make it that way that when you select code, it regulary selects text as it is now in Stash, but if you would like to leave a comment on multiple lines, you click on the line numbers on the left of the code. This would make it the best of both worlds.

              Unassigned Unassigned
              6a4cdb8c-6197-4edf-85c0-023c85ff896d Deleted Account (Inactive)
              Votes:
              429 Vote for this issue
              Watchers:
              164 Start watching this issue

                Created:
                Updated:
                Resolved: