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

Ability to change the author of a pull request

    XMLWordPrintable

Details

    • 256
    • 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.

    Description

      Atlassian status as of Feb 2022

      Hi everyone,

      Thanks for your feedback, passion, and advocacy for this suggestion. Please accept our apologies for allowing this issue to remain open without a clear answer from us.

      We would love to allow changing pull request authors in Bitbucket Data Center. However, we made a decision that this improvement is the wrong direction for our product. We remain committed to being an open company, whether it's with regards to feature requests or bugs in our software. 

      So what are we doing instead? We remain committed to helping software teams deliver high-quality software faster in an increasingly competitive world. We believe that great developer tools are a key element of modern software development. To that end, we've made a lot of improvements last year and are planning to work in the following areas that help with problems development teams face now:

      • Performance and scaling to support growth
      • Security and compliance features
      • Innovations around developer productivity
      • Integrations between Atlassian and other leading products

      Cheers,

      Anton Genkin
      Product Manager - Bitbucket Data Center & Server

      Copied the text of Issue BB-13100
      It should be possible to edit/change the pull request author.

      Use case: When a developer has signaled (e.g., via JIRA issue status) that a branch is ready for review but forgotten to create a pull request, the reviewer should be able to create a pull request and then change its author to the developer. Without the ability to edit, the reviewer has to pick from two or three bad options:

      delay the review until the developer creates a pull request (may take a few days!)
      create a pull request with reviewer as an author, which allows the review to proceed but screws up subsequent interaction in many ways
      review the branch without creating a pull request, which means review comments are going to be attached to individual branch commits (among other problems).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              a30bcffef444 Patrick Schaller
              Votes:
              155 Vote for this issue
              Watchers:
              69 Start watching this issue

              Dates

                Created:
                Updated: