Workzone pull request reviewer groups yields to the nature of every team and enterprise - people come and go and constantly move in and out of teams. Defining reviewer groups as opposed to a set of fixed pre-defined reviewers allows for smooth

Workzone pull request reviewer groups cater to the flow of every team and enterprise – people come and go and constantly move in and out of teams. Use Workzone to define reviewer groups as opposed to a set of fixed pre-defined

Workzone for Bitbucket allows you to control your SCM process, when and how changes can be pushed, and how reviewers and groups are automatically added to new pull requests. Configure pre-defined casual, mandatory and suggested reviewers and groups for pull

Workzone implements fine-grained pull request merge control per branch or branch pattern. Workzone can merge the pull request automatically when all or a percentage of reviewers have approved and/or on successful build results. Workzone can delete the source branch of

Your code is a document. Merging Pull Requests in Bitbucket is basically merging documents, right? Workzone now let's you digitally sign Pull Request Approvals with username and password. It can even be configured to only allow a merge to take place

Automate your Bitbucket Flow - Workzone Automerge CI Integration Auto-Merge with Continuous Integration Systems Workzone can be set up to automatically merge Pull Request triggered by build results. For example you have a user based review and approval process (see above 'Branch Reviewers')

A new level maturity for your SCM process. Control the Pull Request Merge Button Among other popular feature requests Workzone for Bitbucket  introduces tighter control over the Pull Request merge-button. Ever wondered why that merge button was 'hot' while the Pull Request was