We have our own plugin, which is more detailed. And now we have races in reviewers selector on "page creating pull request".
If our plugin get response on rest after default plugin, we see "our reviewers" and vice versa.
So, we need to disable default plugin to use our.
Screenshot from 2016-07-20 15:55:48.png
2. Default plugin response
Screenshot from 2016-07-20 15:51:59.png
You can disable the Bitbucket Default Reviewers Plugin under System in Manage add-ons. This will disable all of the bundled default reviewer functionality.
Out of curiosity, what features does your custom plugin provide that we're not? Perhaps we can create a feature request for this to improve the built in one.
We repeat google-owners logic https://www.chromium.org/developers/owners-files, and retrieve reviewers from closest owner file with several optimizations. May be we could try to upstream our plugin?
I see that I could disable Bitbucket Default Reviewers Plugin in "Manage Addons", but also I see Warning that it is not recommended to disable System installed plugins. But seems that this plugin is not very important, so, the question of my topic in other words - Does it safe to disable default-reviewers plugin?
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs