Required scopes changed:
- Added: project:admin
Required scopes changed:
Workzone 8.4.10 fixes a problem with displaying the correct Workzone merge-check results regarding reviewer group quotas.
Workzone 8.4.10 fixes a problem with displaying the correct Workzone merge-check results regarding reviewer group quotas.
Workzone 8.4.9 fixes merge veto message content for specific group quota merge conditions.
Workzone 8.4.8 fixes a regression when selecting reviewers rules by priority.
Workzone 8.4.8 fixes a regression when selecting reviewers rules by priority.
Workzone 8.4.6 fixes a few dark theme issues.
It's also possible to define a custom help and support center url.
Workzone 8.4.4 allows to clone existing Workzone settings such as
to a new branch or branch pattern.
This can safe a lot of time when cloning existing settings to be applied to a new branch or branch pattern.
Workzone 8.4.4 allows to clone existing Workzone settings such as
to a new branch or branch pattern.
This can safe a lot of time when cloning existing settings to be applied to a new branch or branch pattern.
Workzone 8.4.3 fixes a small problem for digital signature approvals.
Workzone 8.4.3 fixes a small problem for digital signature approvals.
Workzone 8.4.1 features some small workflow improvements:
Workzone 8.4.1 features some small workflow improvements:
Workzone 8.4 is a feature release packed with goodies
Workzone 8.4 is a feature release packed with goodies
Workzone 8.3.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
Workzone 8.3.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
Workzone 8.3.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
Workzone 8.3.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
Required approval counts for file/path reviewers and groups can now be configured in Workzone Reviewers > Files/Paths.
In file/path reviewers configuration enter a user or group and check 'Require approvals' to enable an approval quota for this file/path only.
Required File/Path quotas will be evaluated as merge-checks along with all other Workzone merge conditions for matching pull requests.
Required approval counts for file/path reviewers and groups can now be configured in Workzone Reviewers > Files/Paths.
In file/path reviewers configuration enter a user or group and check 'Require approvals' to enable an approval quota for this file/path only.
Required File/Path quotas will be evaluated as merge-checks along with all other Workzone merge conditions for matching pull requests.
Workzone 8.2.1 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
Workzone 8.2.1 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
Workzone 7.7 delivers a much needed enterprise feature that facilitates ordering pull request reviewer, signature and (auto)merge rules by priority.
The first rule that matches a pull request's source and destination branch will be executed.
Place rules with close or direct branch matching expressions at the top of the list and the catch-all rule at the bottom. For example:
1. (release/current > main) >> reviewers: team1, qa-group
2. (release/* > main) >> reviewers: qa-group
3. ( > main) >> reviewers: bot-reviewer
In this case if someone creates a pull request from any branch other than release/* a bot user gets assigned. Any pull request from release/current gets reviewers groups team1 and qa-group, but if the pull request source branch matches anything else than release/current only qa-group is added as reviewers.
All reviewer, signature approval and (auto)merge rules follow the same match by priority approach.
Workzone 7.7 delivers a much needed enterprise feature that facilitates ordering pull request reviewer, signature and (auto)merge rules by priority.
The first rule that matches a pull request's source and destination branch will be executed.
Place rules with close or direct branch matching expressions at the top of the list and the catch-all rule at the bottom. For example:
1. (release/current > main) >> reviewers: team1, qa-group
2. (release/* > main) >> reviewers: qa-group
3. ( > main) >> reviewers: bot-reviewer
In this case if someone creates a pull request from any branch other than release/* a bot user gets assigned. Any pull request from release/current gets reviewers groups team1 and qa-group, but if the pull request source branch matches anything else than release/current only qa-group is added as reviewers.
All reviewer, signature approval and (auto)merge rules follow the same match by priority approach.
Workzone 8.1.0 adds a 'Start' tab to the Workzone configuration page where new users can take tutorials, find help and links to documentation. Read more ..
Workzone 8.1.0 adds a 'Start' tab to the Workzone configuration page where new users can take tutorials, find help and links to documentation. Read more ..
Workzone 8 is 100% compatible with Bitbucket 8.
Do not install into a Bitbucket 7 instance.
Workzone 8 is 100% compatible with Bitbucket 8.
Do not install into a Bitbucket 7 instance.
Workzone 7.9.10 fixes a problem with displaying the correct Workzone merge-check results regarding reviewer group quotas.
Workzone 7.9.10 fixes a problem with displaying the correct Workzone merge-check results regarding reviewer group quotas.
Workzone 7.9.4 allows to clone existing Workzone settings such as
to a new branch or branch pattern.
This can safe a lot of time when cloning existing settings to be applied to a new branch or branch pattern.
Workzone 7.9.4 allows to clone existing Workzone settings such as
to a new branch or branch pattern.
This can safe a lot of time when cloning existing settings to be applied to a new branch or branch pattern.
Workzone 7.9.3 fixes a small problem for digital signature approvals.
Workzone 7.9.3 fixes a small problem for digital signature approvals.
Workzone 7.9.1 features some small workflow improvements:
Workzone 7.9.1 features some small workflow improvements:
Workzone 7.9 is a feature release packed with goodies
Workzone 7.9 is a feature release packed with goodies
Workzone 7.8.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
Workzone 7.8.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
Workzone 7.8.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
Workzone 7.8.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
Required approval counts for file/path reviewers and groups can now be configured in Workzone Reviewers > Files/Paths.
In file/path reviewers configuration enter a user or group and check 'Require approvals' to enable an approval quota for this file/path only.
File/Path quotas will be evaluated as merge-checks along with all other Workzone merge conditions for matching pull requests.
Required approval counts for file/path reviewers and groups can now be configured in Workzone Reviewers > Files/Paths.
In file/path reviewers configuration enter a user or group and check 'Require approvals' to enable an approval quota for this file/path only.
File/Path approval quotas will be evaluated as merge-checks along with all other Workzone merge conditions for matching pull requests.
Workzone 7.7.2 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
Workzone 7.7.2 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
Workzone 7.7 delivers a much needed enterprise feature that facilitates ordering pull request reviewer, signature and (auto)merge rules by priority.
The first rule that matches a pull request's source and destination branch will be executed.
Place rules with close or direct branch matching expressions at the top of the list and the catch-all rule at the bottom. For example:
1. (release/current > main) >> reviewers: team1, qa-group
2. (release/* > main) >> reviewers: qa-group
3. ( > main) >> reviewers: bot-reviewer
In this case if someone creates a pull request from any branch other than release/* a bot user gets assigned. Any pull request from release/current gets reviewers groups team1 and qa-group, but if the pull request source branch matches anything else than release/current only qa-group is added as reviewers.
All reviewer, signature approval and (auto)merge rules follow the same match by priority approach.
Workzone 7.7 delivers a much needed enterprise feature that facilitates ordering pull request reviewer, signature and (auto)merge rules by priority. The first rule that matches a pull request's source and destination branch will be executed.Place rules with close or direct branch matching expressions at the top of the list and the catch-all rule at the bottom. For example:
1. (release/current > main) >> reviewers: team1, qa-group
2. (release/* > main) >> reviewers: qa-group
3. ( > main) >> reviewers: bot-reviewer
In this case if someone creates a pull request from any branch other than release/* a bot user gets assigned. Any pull request from release/current gets reviewers groups team1 and qa-group, but if the pull request source branch matches anything else than release/current only qa-group is added as reviewers.All reviewer, signature approval and (auto)merge rules follow the same match by priority approach.
Workzone 7.6.0 adds a 'Start' tab to the Workzone configuration page where new users can take tutorials, find help and links to documentation. Read more ..
Workzone 7.6.0 adds a 'Start' tab to the Workzone configuration page where new users can take tutorials, find help and links to documentation. Read more ..
Workzone 7.5.3 fixes 2 issues with
Workzone 7.5.3 fixes 2 issues with
Workzone 7.5.2 fixes a problem with automatic pull request merge after pull request task completion.
Workzone 7.5.2 fixes a problem with automatic pull request merge after pull request task completion.
Workzone 7.5.1 features performance improvements for processing incoming build results.
Workzone 7.5.1 features performance improvements for processing incoming build results.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Workzone 7.4.2 fixes a UI problem with displaying reviewer configurations.
Improved Workzone swagger openapi descriptions.
Workzone 7.4.2 fixes a UI problem with displaying reviewer configurations.
Improved Workzone swagger openapi descriptions.
Workzone 7.4.1 fixes a UI problem when editing merge configurations.
Note: Workzone 7.4.1 is compatible with Bitbucket 7.13+
Workzone 7.4.1 fixes a UI problem when editing merge configurations.
Note: Workzone 7.4.1 is compatible with Bitbucket 7.13+
Workzone 7.4 supports Bitbucket repository reviewer groups that have been introduced since Bitbucket 7.13
Make Workzone part of your scaled agile framework (SAFe+) transformation and create reviewer groups per project and/or repository. Workzone branch/module/path/file reviewer groups can now be based in your AD or repository reviewer groups.
Repository reviewer groups may also be included in advanced Workzone merge conditions just like AD groups.
Note: Workzone 7.4+ only works with Bitbucket 7.13 or higher
Workzone 7.4 supports Bitbucket repository reviewer groups that have been introduced since Bitbucket 7.13
Make Workzone part of your scaled agile framework (SAFe+) transformation and create reviewer groups per project and/or repository. Workzone branch/module/path/file reviewer groups can now be based in your AD or repository reviewer groups.
Repository reviewer groups may also be included in advanced Workzone merge conditions just like AD groups.
Note: Workzone 7.4+ only works with Bitbucket 7.13 or higher.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Workzone 7.3.2 fixes a UI problem when editing merge configurations.
Workzone 7.3.2 fixes a UI problem when editing merge configurations.
Workzone version 7.3.1 introduces editing file and module reviewers as well as various UI and UX improvements
Workzone version 7.3.1 introduces editing file and module reviewers as well as various UI and UX improvements
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings.
The most specific setting will be applied. For example if enforcing merge conditions is enabled globally, it can be disabled on repository level. At project level the configuration can be set to
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings.
The most specific setting will be applied. For example if enforcing merge conditions is enabled globally, it can be disabled on repository level. At project level the configuration can be set to
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
Workzone 7.2.5 fixes a problem with auto-merging pull requests from repository forks.
Workzone 7.2.5 fixes a problem with auto-merging pull requests from repository forks.
Workzone 7.2.4 fixes a security vulnerability when displaying git branch names.
Workzone 7.2.4 fixes a security vulnerability when displaying git branch names.
Workzone 7.2.3 processes build results from Bamboo and other CI systems via multiple REST API endpoints.
Workzone 7.2.3 processes build results from Bamboo and other CI systems via multiple REST API endpoints.
Workzone 7.2.2 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
Workzone 7.2.2 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
UI bugfix for Bitbucket 7.7+
UI bugfix for Bitbucket 7.7+
Workzone 7.2.0 improves security for REST API endpoints and fixes merge-check message content for some Workzone merge condition expressions.
Workzone 7.2.0 improves security for REST API endpoints and fixes merge-check message content for some Workzone merge condition expressions.
Allow AD groups with '#' in their name to be used for reviewer groups and in Workzone merge conditions.
Allow AD groups with '#' in their name to be used for reviewer groups and in Workzone merge conditions.
Workzone 7.0 is a Bitbucket 7.x compatibility release.
Workzone 7.0 is a Bitbucket 7.x compatibility release.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Not all (100%) of Workzone mandatory reviewers have to approve.Use 'mandatoryApprovalCount >= N' to allow partial mandatory approvals in Workzone advanced merge conditions. Learn more
Use mandatory reviewers as gatekeeper reviewers. Often it is sufficient if one or two of them approve a pull request.
Workzone version 6.6.1 introduces editing file and module reviewers as well as various UI and UX improvements
Workzone version 6.6.1 introduces editing file and module reviewers as well as various UI and UX improvements
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings.
The most specific setting will be applied. For example if enforcing merge conditions is enabled globally, it can be disabled on repository level. At project level the configuration can be set to
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings.
The most specific setting will be applied. For example if enforcing merge conditions is enabled globally, it can be disabled on repository level. At project level the configuration can be set to
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
Workzone 6.5.6 fixes a problem with auto-merging pull requests from repository forks.
Workzone 6.5.6 fixes a problem with auto-merging pull requests from repository forks.
Workzone 6.5.5 fixes a security vulnerability when displaying git branch names.
Workzone 6.5.5 fixes a security vulnerability when displaying git branch names.
Workzone 6.5.3 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
Workzone 6.5.3 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
Workzone 6.5.2 allows for workzone originated pull-request merge-conflict notifications to be turned off.
This is helpful for larger instances when lots of pull-request rescope events take place.
Workzone 6.5.2 allows for workzone originated pull-request merge-conflict notifications to be turned off.
This is helpful for larger instances when lots of pull-request rescope events take place.
Workzone 6.5.1 fixes a problem with pull request approval digital signatures.
Workzone 6.5.0 improves app related REST API security.
Workzone 6.5.0 improves app related REST API security.
Workzone 6.4.1 fixes a problem with workzone group quotas for group names with hash (#)
Workzone 6.4.1 fixes a problem with workzone group quotas for group names with hash (#)
Workzone 6.4 improves the way mandatory file path reviewers and groups are added to pull requests.
Workzone 6.4 improves the way mandatory file path reviewers and groups are added to pull requests.
Workzone 6.3 now supports absolute pull request reviewer approval counts in merge conditions. For example
'approvalCount > 1'
Will merge (or allow a pull request to be merged) when more than one reviewer have approved.
This enables merge checks where pull request need at least 'some' approval before they can be merged.
Workzone 6.3 now supports absolute pull request reviewer approval counts in merge conditions. For example
'approvalCount > 1'
Will merge (or allow a pull request to be merged) when more than one reviewer have approved.
This enables merge checks where pull request need at least 'some' approval before they can be merged.
Version 6.2.1 fixes a UI problem when resetting Workzone repository properties (hooks) to Workzone project properties settings.
Version 6.2.1 fixes a UI problem when resetting Workzone repository properties (hooks) to Workzone project properties settings.
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
Workzone 6.1.2 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
Workzone 6.1.2 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
Workzone 6.1.1 now recognizes AD group names with whitespace like 'Test Group 1'
Workzone 6.1.1 now recognizes AD group names with whitespace like 'Test Group 1'
Workzone 6.1.0 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
Workzone 6.1.0 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
Fixes an Internet Exploder 11 JS problem
Fixes Internet Exploder 11 JS problem
Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
Workzone 6.0 is fully compatible with Bitbucket 6.
Workzone 6.0 is fully Bitbucket 6 compatible.
Minor UI changes and improvements for compatibility.
Workzone 5.11.2 fixes a security vulnerability when displaying git branch names.
Workzone 5.11.2 fixes a security vulnerability when displaying git branch names.
Workzone 5.11.1 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
Workzone 5.11.1 is a performance improvements release.
On pull request rescope events (a pull request's target or source branch commit hash changes) Workzone no longer performs a merge-check by default. The feature can be turned on in global admin Workzone settings. More on performance tuning ...
Workzone 5.11 now supports absolute pull request reviewer approval counts in merge conditions. For example
'approvalCount > 1'
Will merge (or allow a pull request to be merged) when more than one reviewer have approved.
This enables merge checks where pull request need at least 'some' approval before they can be merged.
Workzone 5.11 now supports absolute pull request reviewer approval counts in merge conditions. For example
'approvalCount > 1'
Will merge (or allow a pull request to be merged) when more than one reviewer have approved.
This enables merge checks where pull request need at least 'some' approval before they can be merged.
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files.
Refined configuration of reviewers for files and modules:
Your development team/group reviews all files except src/main/test.
The test team reviews test files.
Workzone 5.9.4 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
Workzone 5.9.4 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
Workzone 5.9.3 now recognizes AD group names with whitespace like 'Test Group 1' .
Workzone 5.9.3 recognises whitespace in AD group names like 'Test Group 1'
Version 5.9.2 fixes a repository hook that can blocks bitbucket file editor changes to files for pull request source branches.
It now behaves the same as blocking changes from git CLI push commands to pull request source branches.
Version 5.9.2 fixes a repository hook that can blocks bitbucket file editor changes to files for pull request source branches.
It now behaves the same as blocking changes from git CLI push commands to pull request source branches.
Workzone 5.9.1 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
Workzone 5.9.1 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
Workzone 5.9.0 introduces configuration change audit logging for
All events are published with HIGH audit logging priority.
Workzone 5.9.0 introduces configuration change audit logging for
All events are published with HIGH audit logging priority.
Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
Workzone version 5.8.2 fixes a problem with toggles in Safari and Edge browsers
Version 5.8.2 fixes a problem with toggles in Edge and Safari browsers
Workzone 5.8.1 improves performance when merging pull requests via incoming successful build results.
The maximum age of open pull requests that can be merged by Workzone can now be limited in Workzone's global config. Default is unlimited - as was the case so far.
Workzone 5.8.1 improves performance when merging pull requests via incoming successful build results.
The maximum age of open pull requests that can be merged by Workzone can now be limited in Workzone's global config. Default is unlimited - as was the case so far.
Workzone 5.8.0 is officially approved by Atlassian for
Workzone 5.7.1 is a bugfix release around digital signatures for pull requests.
* fix display of Sign & Approve button when pull request is declined and re-opened
* don't show Sign & Approve button to author
Workzone version 5.7.1 is
== F U L L Y D A T A C E N T E R C O M P A T I B L E ==
Workzone 5.7 proudly introduces
Note: Workzone 5.7 is Datacenter compatible (as you would expect)
Version 5.6.3 fixes a Workzone auto-merge bug with mandatory reviewers are part of the pull request reviewers set.
Workzone version 5.6.2 improves auto-merge when watching incoming (successful) build results.
The release improves the merge-veto message content shown when pull requests can't be merged due to Workzone merge-conditions not being met.
Version 5.6.0 of Workzone features a new merge condition element
Workzone now also has an improved (auto)-merge configuration UI.
Configure Workzone reviewers, signed approvals and (auto) merge conditions PROJECT-wide.
Repositories inherit project wide settings or define their own settings.
Easily switch between project settings and repo settings via copy and reset.
Workzone 5.4.0 fixes a problem where the number of groups a reviewer could be a member of was hard-limited to 99. This is now configurable in Workzone global administration settings.
This makes sure that a reviewer's approval is counted towards _all_ groups (within the set limit) when evaluating a Workzone merge condition.
Same as version 5.3.1 - but this release artifact contains the Workzone JAR file
Version 5.3.1 fixes a problem where new auto-merge configurations set their merge-strategy incorrectly.
Any Workzone auto-merge configuration that has been created with Workzone 5.3.0 should be re-entered. We are very sorry for the inconvenience. Please contact support at izymes dot com if you need assistance.
Workzone 5.0.3 features
Bugfixes
Specify advanced merge conditions with a group (approval) quota bound to specific groups like groupQuota['abba'] > 2
Merge conditions can now elevate the number of approvals required for specific groups or sets of group over the general group quota. Read more ...
Workzone 5.0.1 provides compatibility with Bitbucket Server 5
Workzone 4.6.4 allows admins to configure the maximum number of reviewer groups a user can be in. This was limited to 99 before. However users in larger organization may have more than 99 group memberships.
Version 4.6.2 features some performance improvements for Workzone's CI server integration (Bamboo, Jenkins etc) when processing large amounts of build results.
* When a pull request is marked with 'Needs Work' - veto merging the pull request (via Workzone global setting)
* Bugfix: ignore file-path reviewer group quota merge condition if changeset does not include file or path pattern
Specify advanced merge conditions with a group (approval) quota bound to specific groups like groupQuota['abba'] > 2
Merge conditions can now elevate the number of approvals required for specific groups or sets of group over the general group quota. Read more ...
TLDR;
Workzone version 4.4.4 fixes a digital signature approval problem.
The nitty-gritty:
Workzone 4.4.3 aims at performance improvements when detecting potential merge conflicts.
When a PR is updated (rescoped) with new files, all reviewers responsible for these directories/files are also added to the PR.
Workzone 4.4.0 features file and directory pull request reviewers. Watch it in action
Fixes for
Attempt to auto-merge a Pull Request after a reviewer has been demoted to participant. This happens when the reviewer left a comment and is later removed as a reviewer.
Version 4.3.2 adds the much requested feature to define Workzone merge conditions but prevent Workzone from automatically merging a PR.
Configure merge conditions, but leave the auto-merge user field blank. Submit the configuration.
This release features
Fixes a bug for Immediate Auto-merge of Pull Requests that prevented the (immediate) merge if reviewers were defined for other branches than the target branch of the PR.
Workzone 4.2.2 is a minor bugfix release
This release features some minor UI improvements around digital signatures for Pull Request approvals.
Digitally Signed Approvals
Watch our digital signed approvals action video.
Use cases and signed Pull Requests in action can be found in our blog post:
Get your SCM process FDA (Part 11) Compliant with Workzone Signed Approvals.
Workzone 4.6.3 allows admins to configure the maximum number of reviewer groups a user can be in. This was limited to 99 before. However users in larger organization may have more than 99 group memberships.
Version 4.6.1 features some performance improvements for Workzone's CI server (Bamboo, Jenkins etc) integration when processing large amounts of build results.
Minor UI bugfix - saving reviewer configuration source branch correctly. Thanks to Sylvia Yee for reporting this bug.
Release 4.1.1 adds the long awaited feature to publish / bulk change Workzone repository settings to other project's repositories.
'Workzone Publish' will publish configurations to _all_ repositories belonging to the selected target projects.
Enjoy improved productivity by configuring one repository and rolling out its settings to selected (or all) project's repositories.
Release 4.1.0 adds the long awaited feature to publish / bulk change Workzone repository settings to other project's repositories.
'Workzone Publish' will publish configurations to _all_ repositories belonging to the selected target projects.
Enjoy improved productivity by configuring one repository and rolling out its settings to selected (or all) project's repositories.
This bug fix release addresses a problem when adding a reviewer configuration with ref (branch) patterns.
Version 4.0.0 of Workzone is compatible with Bitbucket Server 4.0.0.
Please do not use Workzone 4.0.0 for Stash.
Fixes a bug for Immediate Auto-merge of Pull Requests that prevented the (immediate) merge if reviewers were defined for other branches than the target branch of the PR.
Workzone 3.1.3 is a bugfix release for Stash 3.5 - 3.11.
Support mixed case group names. Special thanks to J.T. Conklin (Dell) for all the support.
This minor bug fix release solves a problem when the Workzone auto-merge condition 'group quota' contains a '%'.
Group quota merge condition must be a total number of approvals for each group that is defined in workzone reviewers. Per cent '%' is not accepted as finding _all_ group members would be too expensive for large AD/LDAP user directories.
This release includes a new Pull Request auto-merge feature.
Workzone 3.0 is a major release featuring auto-merge conditions extensions
For a quick intro watch the tutorial.
The auto-merge user's branch permissions are checked correctly.
(Note that core Stash 3.10.0 and 3.10.1 have a bug the prevents Workzone to set an auto-merge user if branch permissions are defined for this user - https://jira.atlassian.com/browse/STASH-7607)
Version 2.4.6 fixes a branch-deletion problem after auto-merge with Stash 3.10.
This release contains several performance improvements w.r.t.
This is a feature release enables admins to set the limit of reviewers per reviewer group.
This release also enforces license checks when reviewers are added to new Pull Requests and when attempting to merge Pull Requests automatically.
This minor bug fix release improves incoming CI server build status processing.
Bugfixes for
Fix for undocumented and un-announced Stash 3.8 email template removals.
Workzone 2.4.1 improves overall performance when checking Pull Request related build results from CI servers.
Please upgrade to this version if you get lots of build result traffic from a CI server like Bamboo or Jenkins.
This is a major feature release introducing three new Workzone global configurations for
Read our blog on how you can move your SCM process to the next level of maturity by blocking accidental or intentional pre-mature Pull Request merges.
This is a CI (Build System/Bamboo) integration bug fix release.
Ability to set/edit auto merge quota parameter.
Workzone can automatically suggest Reviewers and add them to Pull Requests. Don't let top committers miss out on reviewing Pull Request change sets! Workzone looks at each file in the Pull Request, identifies top committers (counting commit frequency based on committer's email) and adds them as reviewers automatically.
Check out the release notes and the documentation for more details.
This is a minor bug fix release.
Urgent bug fix release that deals with version 2.2 (mandatory reviewers) upgrade problems.
This is an urgent bug fix release for version 2.2
Problems resolved
Workzone version 2.2 is a major feature release. Add mandatory reviewers/groups to a Pull Request to ensure all mandatory reviewers MUST approve before the Pull Request can be merged automatically by Workzone.
If someone removes a mandatory reviewer through editing the Pull Request, the removed mandatory reviewer(s) are added back through Workzone.
This is a minor bugfix release addressing a change in email notification templates with Stash 3.4.x
Workzone 2.1.3 is a bug fix release
With this new feature release you can now refine the scope of your Pull Request reviewer and auto-merge configuration.
Examples:
Read more in the release blog post.
Improved event handling to allow Stash and Workzone to scale better for larger instances.
New shiny logo
We are proud to announce Workzone for Stash Datacenter. Version 2.1.0 is a major release that features cluster-safe operations.
Workzone for Stash 2.0.5 is a minor improvements release including
This is a minor Workzone bug fix release for
Minor bug fix release
Version 2.0.2 is a minor bug fix and small feature release
The new Workzone auto-merging features have the following options
Notifiactions:
The release is a licensed version of Workzone for Stash
This is a back port from Workzone for Stash 2.x to Workzone 1.3.x
New in this release
In this exciting new version Workzone for Stash introduces branch ref patterns.
Fixed in this release
Setting the auto-merge user works when various patterns for branch permissions are set.
New in this release
In this exciting new version Workzone for Stash introduces branch ref patterns.
New in this release
Workzone for Stash just got better :)
Fixed in this release
When adding a auto-merge user for a branch, permissions check respects branch permission advanced patterns.
New in this release
This is a compatibility release for Stash 2.8
Workzone lets you configure auto-merge to trigger a merge automatically even if not all reviewers have approved. Specify a percentage of needed approvals and once the quota is reached, the PR will be merged.
Workzone auto-merge warns if Stash Pull Requests for a repository are configured to have a minimum number approvers - then auto-merge may not be successful. When using Workzone auto-merge it is not recommended to enforce Stash Pull Request required approval numbers.
Workzone is now compatible with Stash 2.2 through 2.7.x. Support for Stash 2.1. has been dropped due to dependency on the Stash required approvals hook that was introduced in Stash 2.2.
Version 1.2.6 fixes a regression bug of version 1.2.5 discovered while testing. Please refrain from using version 1.2.5. Apologies for the inconvenience.
This is a feature and Stash 2.6.x compatibility release.
Features
This is a minor bug fix release.
This bugfix release improves adding pre-configured reviewers when a Pull Request originates from a forked repository.
This release overrides the previous version 1.2.1 which contained a merge error. Sorry for the inconvenience.
This is a minor feature and bug fix release
This is a Stash 2.5 compatibility release.
Version 1.1.0 is compatible with Stash 2.1 through to 2.4
Initial Codegeist Release