-
Bug
-
Resolution: Fixed
-
Low
-
4.1.0
-
Severity 3 - Minor
-
As a Stash/Bitbucket Server User I want to be able to delete my personal fork even though I have a pull request (open OR declined) to an upstream repo to which I no longer have permission to access.
HTR
- Fork a repo to your personal project.
- Open a PR from your fork to the upstream repo.
- Have a user with Project Admin or higher perms remove your permission to the upstream repo.
- Push another change to your personal fork that would update the PR (the PR shouldn't be visible to you anymore at this point).
- Delete your fork.
Expected Result
My forked repo is deleted successfully.
Actual Result
Fork deletion fails and an error modal is displayed:
Repository deletion was canceled.
Pull requests involving ~DROHAN/blues could not be cleaned up. The repository may not be delete
When personal forks first shipped in Stash 2.4.0, it was possible to delete a personal fork (or any other fork) regardless of what pull requests existed (regardless of their state). It appears, during the 3.x changes necessary to support clustered installations, that ability was regressed.
Given that this is a regression of behavior that used to work, I've reclassified this as a bug, which I consider it to be.
Best regards,
Bryan Turner
Atlassian Bitbucket