Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-10448

Auto-unapproved after push should be marked as such

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Pull Requests
    • None
    • 3
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When dev1 has opened a pull request from e.g. a feature branch to the develop branch, then dev2 has approved the pull request, and afterwards dev1 pushes another change to the branch, the pull request is marked as unapproved. This is sensible behaviour, but there is one thing about it that I don't like, and which leads to confusion: It is not obvious, that the "Unapproved" was an automatic action done by the system. It looks like the person, who had previously approved the pull request, had now manually unapproved it again, without providing a comment.

      IMO it would be much better if there would be an additional remark (e.g. instead of UNAPPROVED, the label could read UNAPPROVED AUTOMATICALLY or something).

              Unassigned Unassigned
              37198d1170ad Patrick Nagel
              Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: