G2

Rohan K.

Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

6/25/2024

"Enhancing automation experience for our Bitbucket cluster"

5/5

What do you like best about Workzone: PullRequest Workflow?

It provides pull request merge controls:

- Control merge based on merge conditions including required approvals from reviewers and groups

- Enforce required approval counts

- Merge a pull request automatically when all conditions are met

All of this saves time in setting up custom automation rules using Scriptrunner or a similar tool which also has additional overhead of learning a scripting language like Groovy, etc Review collected by and hosted on G2.com.

What do you dislike about Workzone: PullRequest Workflow?

It sometimes add complications while implementing conditions for pull request merge and end users are not aware of what is blocking their PR merges. Review collected by and hosted on G2.com.

What problems is Workzone: PullRequest Workflow solving and how is that benefiting you?

It is helping with automation like configuring pre-defined reviewers and groups for branches and file patterns. Each Pull Request for that branch will include these reviewers automatically. This saves time in setting up custom automation rules using Scriptrunner or a similar tool which also has additional overhead of learning a scripting language like Groovy, etc.

It also helps in controlling the Pull Request merge process, wherein until a pre-defined set of conditions are met, one cannot merge the pull request. This helps in improving the quality of code merged into the main/master branch as well. Review collected by and hosted on G2.com.