1. Atlassian Avatar Atlassian
  2. Project: Atlassian
  3. stash-auto-unapprove-plugin
  4. Issues

Auto Unapprove Plugin DC Compatibility

Issue #22 resolved
Former user created an issue

Is there any intention to upgrade this add-on to be Data Centre compatible? If yes, then when will this be available? If not, will this add-on work in Data Centre?

Thanks.

Comments (15)

  2. Bryan Turner Account Deactivated

    Auto-unapprove has been submitted for DC verification, which is pending. ("Internal" apps go through the same verification process as any other app.)

  3. Former user Account Deleted

    Thanks for the answer. Is there any timeline or do you have when the verification will be through?

  4. Bryan Turner Account Deactivated

    The build infrastructure for this has bitrotted somewhat since the last release, so we're getting that updated. At that point I'll release a 3.1.0 of this app which includes the fix for #18. At that point it should be acceptable for certification, so I'd hope to get everything resolved in short order after that.

  8. Christopher Schulte

    Any progress here? Our IT won’t allow the usage of this addon until it has been certified as data center compatible.

    Which is very sad, since Bitbucket without this feature is not really usable..

  10. rgoossens

    Hi @{557057:f752a17a-2c16-46d3-8886-5b8dbcfa57f1} , @Kristy Hughes ,

    Can you please let us know what the timeline is on the DC verification? This plugin blocks migration from Server to DC for users who are relying on this functionality.

    Alternatively, any information of plans on making this functionality part of the core like in the cloud version of Bitbucket would even be better!

    Cheers, Ruud

    ‌

  13. venkata subramanyeswara Rao Gogineni

    Hi,

    We at our organization use Bitbucket (Cloud/Datacenter set-up) and have noticed that when a user approves a pull request, that approval remains even after the underlying branch has been updated. This is not good practice (in perspective of a teams that use our Bitbucket) as the approve has not had chance to validate the latest changes.

    Please let me know if more info is needed .. the workflow what team is looking for:

    1. pull request raised by person X
    2. pull request approved by person Y
    3. pull request commented by person Z asking for a change to be made
    4. underlying branch of the pull request modified and pushed to BitBucket by person X
    5. At this point the code in the pull request has changed, but person Y's approval for the pull request still exists, even though person Y has not seen the latest code pushed in point 4.

    I’m aware that this plugin (https://marketplace.atlassian.com/apps/1211449/auto-unapprove-for-bitbucket-server?hosting=server&tab=overview ) is an example of how it can be done, but this isn't available in Datacenter edition which our Bitbucket requires .. On the other hand, we also don't want to load Bitbucket with plugins.

    So any suggestions across, if not using the plugin that I mentioned above?

    I also had a read through "workzone plugin" , do you think it can help instead?

    1. Push after Pull Request: Enable users to push to branches that have an open outgoing pull requests.
    2. Unapprove Pull Requests on Source Change : When code is pushed to a branch with an outgoing Pull Request, withdraw all approvals for this Pull Request.
    3. Unapprove Pull Requests on Target Change: When code is pushed or merged to the target branch of a Pull Request, withdraw all approvals for this Pull Request

    Thanks in Forehand for your response.

    Regards,
    Venkata GOGINENI

  14. rgoossens

    Bad news guys. Our Atlassian contact got into contact with Bryan and Kristy and they confirmed that there are no updates or timelines for the plugin to be DC certified.

  16. Log in to comment
Assignee
–
Type
enhancement
Priority
minor
Status
resolved
Votes
11
Watchers
16