2,518
Customers have installed this app in at least 2,518 active instances.
    by Atlassianfor Bitbucket Server 5.0.0 - 5.16.0 and more versions
    Versions available for Bitbucket Server 2.5.0 - 2.12.6
    Bitbucket Server 3.0.0 - 4.14.12
    Supported
    Atlassian supports this app.

    Get support

    Get it nowFree app

    Unapprove pull requests automatically when they change

    Unapprove pull requests automatically when they change

    Unapprove pull requests automatically when they change

    Require reapproval of Pull Requests after changes

    Ensure rework is properly addressed

    Better support for iterative review

    Unapproves all reviewers when new commits are pushed to the pull request's source branch, or the pull request is updated to target a different branch.

    Unapproving forces reviewers to return to the pull request and re-approve it, indicating they have verified the new changes.

    Automatic unapproval means developers can iterate on a feature branch until it is ready to be merged, confident that each change has been verified by their designated reviewers.

    More details

    There are no additional details.

    Reviews for cloud

    (25)
    Sign in to write a review
    by Jaroslav Barton on 2017-05-12
    Does not work with BitBucket 5.0.1 DC, unable to enable with following exception in log: 2017-05-12 01:39:38,763 ERROR [ThreadPoolAsyncTaskExecutor::Thread 35] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.atlassian.stash.plugin.stash-auto-unapprove-plugin' org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://135.0:0/META-INF/spring/atlassian-plugins-component-imports.xml]; nested exception is java.lang.IllegalStateException: The bundle is uninstalled.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Jaroslav Barton,

    You may wish to retry with the just-released 3.0.0 version of the add-on, which is compiled and tested against Bitbucket Server 5.0.5.

    by Eric Brown on 2016-05-24
    This should be in stash by default. Wish it had a server default configuration and the ability to override at the repo level. Would make configuration simpler if you wanted all repos but just a few to operate a certain way.
    15 out of 15 found this review helpful
    Was this review helpful?YesNo
    by kanika05 on 2016-05-23
    great
    0 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Peng Shan on 2016-02-29
    Nice one (thumbsup)
    0 out of 3 found this review helpful
    Was this review helpful?YesNo
    by Mark Gillespie on 2015-06-22
    Really needs the ability to ignore merges. Without this, it's mostly useless for our workflow.
    12 out of 16 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Mark Gillespie,

    Versions 2.2.0 (for Bitbucket Server 4.7-4.14) and 3.0.0 (for Bitbucket Server 5.x) introduce a change which uses git patch-id to detect when updates to a pull request don't affect the diff (for example, when pushing a "clean" merge from the target branch to the source branch) and no longer withdraws approvals. Perhaps that will improve your experience?

    Reviews for server

    (25)
    Sign in to write a review
    by Michael Nicholson on 2018-11-28
    This is a problem for us too, as we have 200+ repos spread over several projects. As a workaround I was able to use the REST API to enable this setting in all repos via script. But this will need to be run each time a new repo is added :-/ curl --request POST --user '<user>:<password>' --header 'Content-Type: application/json' --data '{"unapproveOnUpdate": true}' "http://<url>/bitbucket/rest/api/1.0/projects/${project_key}/repos/${repo_key}/${api_url}" We're using Bitbucket Server.
    Was this review helpful?YesNo
    by Cameron Gocke on 2018-11-02
    As others have pointed out, the fact that this has to be set at the repo level rather than the project level severely limits its utility. The feature request to add this to the core (https://jira.atlassian.com/browse/BSERV-8458) was closed out with the justification that you can achieve this behavior using the plugin, but the plugin isn't a viable option if I have to set this behavior on 50-60 repos. If you want to vote for this, go here: https://bitbucket.org/atlassian/stash-auto-unapprove-plugin/issues/16/allow-auto-unapprove-to-be-set-at-the
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by G. Sylvie Davies [bit-booster.com] on 2018-09-26
    Check out "PR-Booster" (paid add-on) for an implementation that supports global and per-project config for this problem, includes the ability to retract on "all commits" vs. "significant commits", as well as the ability to retain "needs work" reviews. https://marketplace.atlassian.com/apps/1214545/pr-booster-for-bitbucket-server
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Mark Finta on 2018-07-19
    Please also put the General Tab that houses this setting at the Project Level.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    by Florian Behrens on 2018-05-17
    Very useful plugin! The only thing that should IMHO be improved is the fact that even a 'Needs Work' status is reset to no status on a new commit. In my perception the term 'unapprove' does not really reflect a state transition from 'Needs Work' to nothing. I'd suggest for the addon to not touch the status 'Needs Work' when a new commit comes in (or make it configurable at the project/repo level) and only reset to nothing (i.e., 'unapprove') when the status is 'Approved'. eyes does not really comply with the add-on title as
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for Data Center

    (25)
    Sign in to write a review
    by Jaroslav Barton on 2017-05-12
    Does not work with BitBucket 5.0.1 DC, unable to enable with following exception in log: 2017-05-12 01:39:38,763 ERROR [ThreadPoolAsyncTaskExecutor::Thread 35] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.atlassian.stash.plugin.stash-auto-unapprove-plugin' org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://135.0:0/META-INF/spring/atlassian-plugins-component-imports.xml]; nested exception is java.lang.IllegalStateException: The bundle is uninstalled.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Jaroslav Barton,

    You may wish to retry with the just-released 3.0.0 version of the add-on, which is compiled and tested against Bitbucket Server 5.0.5.

    by Eric Brown on 2016-05-24
    This should be in stash by default. Wish it had a server default configuration and the ability to override at the repo level. Would make configuration simpler if you wanted all repos but just a few to operate a certain way.
    15 out of 15 found this review helpful
    Was this review helpful?YesNo
    by kanika05 on 2016-05-23
    great
    0 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Peng Shan on 2016-02-29
    Nice one (thumbsup)
    0 out of 3 found this review helpful
    Was this review helpful?YesNo
    by Mark Gillespie on 2015-06-22
    Really needs the ability to ignore merges. Without this, it's mostly useless for our workflow.
    12 out of 16 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Mark Gillespie,

    Versions 2.2.0 (for Bitbucket Server 4.7-4.14) and 3.0.0 (for Bitbucket Server 5.x) introduce a change which uses git patch-id to detect when updates to a pull request don't affect the diff (for example, when pushing a "clean" merge from the target branch to the source branch) and no longer withdraws approvals. Perhaps that will improve your experience?

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    Atlassian provides support for this app.

    Vendor support resources

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 3.0.2 Bitbucket Server 5.0.0 - 5.16.0 Released 2018-12-07

    Summary

    Moves processing to background threads

    Details

    Previously, processing to determine whether to unapprove a pull request after a rescope was performed directly on Bitbucket Server's event threads. Since processing can (in the worst case) take multiple minutes, that can result in the event queue filling up and potentially dropping events.

    Installation

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Auto Unapprove for Bitbucket Server via search. Results include app versions compatible with your Bitbucket instance.
    5. Click Install to download and install your app.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Auto Unapprove for Bitbucket Server versions compatible with your instance, you can look through our version history page.

    Similar apps