The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Don't remove PR approvals on sync/merge from its destination branch?
Phil Wilkinson
I'm New Here 
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 14, 2019 edited
So we'd like to utilise the premium feature in the 'Branch permissions' section titled: "Approvals are reset when the source branch is modified"
Our process is as follows:
- Code is written
- PR is created
- Other devs approve or leave comments
- Once the PR has 2+ approvals, it's ready for testing/QA
- At some point, the work is selected for QA
- The PR is brought up to date with its destination branch
- PR is deployed for testing
- After approval PR is now ready for merging, etc
Now, our tester typically ensures that the branch is up to date with the branch that the PR is pointing at (item 6 on the above process list). This merge/sync updates the source branch and understandably loses all reviewers.
Most of the time, however, the work in the branch (compared to its destination, i.e. diff) has not changed (no conflicts), so this is not at all helpful in practice.
Is there a way to not remove approvals on a sync/merge from its destination branch?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian