improved ACLs for deletion of PRs

The only options that we have at this time are:

• Prevent ALL Pull Request deletions. This is the best option if data retention is an absolute must. PRs can still be declined and will not show up on the default list but could never be deleted with this option

• Prevent Pull Requests from being deleted except for Repository, Project, and System admins. Depending on how you define user permissions this is the best option if you want to still allow for some deletions but want to put some controls around it. For example you might setup an internal request to delete a PR that users could follow that a Repository Admin would then perform the actual delete once all the correct steps were followed and notifications given

• Prevent Pull Requests from being deleted except for the PR Author and all levels of Admins. If you want an author to be able to delete a PR, perhaps because it was opened in error, then using the AUTHOR value in the pullrequest.deletion.role setting will allow for this but there are no additional controls. For example the author could delete a PR they created even if other people had participated, added comments, tasks, etc.

If you have many teams working on the same Bitbucket DC Instance, you run quickly into trouble with opinions of teams weather it should be possible to delete PRs or not at all but also about who can delete PRs and which rules will forbid the deletion of a PR.

We see today a strong need to rework the ACLs in general on Bitbucket to be more enterprise oriented for DC Version of Bitbucket (at least).

Today as Admins and owners of self hosted Bitbucket instances we often have the need to restrict or change permissions for certain functionalities depending on the need of the team. This can be repository level or project level, but not instance level.

Hence we would like to ask to integrate a hardened ACL for PRs (similar maybe to how its done on Branches).

It would be better though to integrate better ACLs in general cause Git Hooks can be manipulated by any admin - hence the ACL wouldn't be really hardened.