Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issue: Incorrect history & notification text when a pull request is auto-unapproved Edited

I have a complaint about how Bitbucket describes automated approval retraction for a changed Pull Request. 

Right now, there isn't a distinction in the PR history or notifications between a reviewing user that deliberately retracts their approval versus when the PR automatically retracts that approval upon the branch receiving a new commit.  Since the reviewer isn't the one actually un-approving the PR, the text as currently shown is incorrect, as it states that the approval retraction was that user's own action.

 

To recreate:

Make a pull request for a branch with commits.

Add a reviewer.  We'll call her "Barb".

Have "Barb" approve the request.

Push a new commit to the branch.

What currently happens:

I receive a notification that "Barb" has marked the PR as unapproved.

The PR overview/history shows that "Barb" marked the PR as unapproved.

What should happen:

The notification should communicate in some manner that Bitbucket has retracted Barb's approval (and the approval of any other reviewers) because a new commit was added to the branch.

The PR overview/history should also show that Bitbucket retracted all approval(s) because a new commit was added to the branch.

1 comment

Your question inspired us to implement an improved "auto-unapprover" in our paid add-on, PR-Booster for Bitbucket Server.

Here's the config screen:

pr-booster.png

And here's the end-result:

pr-booster-history.png

Our add-on allows the auto-unapprover to be enabled globally, per-project, or per-repo.  We also implemented functionality for retaining "needs work" reviews, which normally get dropped the moment the PR receives any new commits.

We use a special "PR-Booster - Approval Reset Bot - New Commits Detected" service user to make the unapprove actions understandable on the PR history.

Install PR-Booster for Bitbucket Server to try this out!

 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

289 views 2 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you