After commit 'Needs Work' status is reset to no status.

[Former user]

Bitbucket Server: Bitbucket v5.13.1 Auto Unapprove for Bitbucket Server Version 3.0.0

After commit 'Needs Work' status is reset to no status. It would be much more useful, if 'Needs Work' status would be available after new commit.

[Kristy Hughes]

Can you please explain what you mean by "It would be much more useful, if 'Needs Work' status would be available after new commit."? The purpose of the 'Needs Work' status is so that it gets reset after someone pushes changes - that way you know its ready for you to re-review. On top of this, you can use iterative review to only show you the changes since you last approved to make it easier to know what's changed.

[Julien Roncaglia]

Need work mean that something need fixing.

The original submitter fixing a typo somewhere shouldn't remove the "Need work" that was made because the PR is needing some big changes.

[Bryan Turner]

Removing "Needs Work" status is a Bitbucket Server behavior, not something this app does. As @KristyHughes has indicated, it's intentional that it's reset after every push. "Needs work" indicates the reviewer has considered the current changes and feels some additional changes are necessary. After new commits are pushed, reviewers need to review the latest changes (which iterative diff helps simplify) and decide whether the necessary rework has been done or not. If not, they mark the pull request as "Needs work" again.

[Bryan Turner]

Closing this, as the behavior in question is not part of this app.