I believe the pull requests are a core element to value add on top of DVCS and always having pull requests visible reenforces the concept to users. If users do not know what it is hopefully they will find out and we have helped spread the concept.
We also are trying to reduce the surface area of Bitbucket. We are trying to remove configuration options, not add new ones. We debated if we should allow the downloads to be configurable and in the end decided not to. The same idea applies to pull requests.
I can see how a project may not want to accept them and therefore does not want the option. However if you are getting PR's is that not a sign that perhaps your community wants to contribute?
I'd also like to be able to disable pull requests. I create a public base repository for the homework that I assign. My students create private forks. Inevitably, one of them accidentally submits a pull request. Suddenly everyone can see their "contributions" -- which should have been private.
Declining the requests doesn't make them disappear.
I have the same problem as the one described by Chris Johnson in 2014. I am about to remove my repository only because I can't delete the pull requests. I will create another one with the same commits, not sure if the forks already created by my students will be able to pull and merge automatically from my repo. I hope so.
I agree with this ticket. I don't understand why it was changed to wontfix. I manage many projects using Bitbucket, Jira, Crucible and Bamboo. I use feature branching strategy as many enterprise companies do. There is absolutely no reason to have pull requests "enabled".
I understand that pull requests are a valid feature for open source projects but still it should be up to the owner to decide if pull requests should be available in his repositories.