Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-19890

Restrict who can decline a pull request

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      Like we have Merge checks in Branch permissions, it would be useful if a similar functionality for who should be allowed to Decline a Pull Request.

      The choices I would be looking for are:

      • Author
      • Reviewer

      Looking at Decline specifically is important as it corresponds to a what-happens-next type of workflow.

      For example:

      • Is the issue still relevant?
      • Should the ticket be updated with a different priority?
      • Mark as `Won't Fix`, etc

      This obviously depends on everyone's workflow, but for the above example it would the the Author's responsibility to do the above changes at the same time of Declining the Pull Request.

      A similar suggestion can be found here:  BCLOUD-12509

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            aa62d28313e3 Antonios Pavlakis
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: