Minor version update
Version history
CloudBitbucket Cloud2023-05-31Minor version update 8.4.1Bitbucket Data Center 8.0.0 - 8.11.02023-06-01Workflow improvements Workzone 8.4.1 features some small workflow improvements:
- When a new commit on the source branch has no effective code changes, for example after a rebase, given approvals are not withdrawn
- Workzone auto-merge diagnostics can be turned on in Workzone admin settings to log more information when an auto-merge failed.
8.4.1Bitbucket Server 8.0.0 - 8.11.02023-06-01Workflow improvements Workzone 8.4.1 features some small workflow improvements:
- When a new commit on the source branch has no effective code changes, for example after a rebase, given approvals are not withdrawn
- Workzone auto-merge diagnostics can be turned on in Workzone admin settings to log more information when an auto-merge failed.
8.4.0Bitbucket Data Center 8.0.0 - 8.11.02023-05-23Feature release - detailed merge-check veto report & secure digital signatures Workzone 8.4 is a feature release packed with goodies
- Detailed Workzone merge veto report: If Workzone vetoes a pull request merge a detailed report is accessible via the pull request page actions side bar. The merge veto report contains all details as to why the current pull request cannot be merged, including missing file/path reviewer approvals
- Additional permission checks for digital signature: additional security filter makes sure that a reviewer that must approve with a digitally signature can not approve the pull request by quickly clicking on the pull request approve button
- Additional merge condition token filePathMergeChecksPass: The Workzone advanced merge condition expression can now incorporate a new condition called filePathMergeChecksPass == true. Use filePathMergeChecks to evaluate file/path reviewer quota checks explicitly. This condition comes into play if the Workzone reviewer file/path configuration has also required approvals per file/path defined.
8.4.0Bitbucket Server 8.0.0 - 8.11.02023-05-23Feature release - detailed merge-check veto report & secure digital signatures Workzone 8.4 is a feature release packed with goodies
- Detailed Workzone merge veto report: If Workzone vetoes a pull request merge a detailed report is accessible via the pull request page actions side bar. The merge veto report contains all details as to why the current pull request cannot be merged, including missing file/path reviewer approvals
- Additional permission checks for digital signature: additional security filter makes sure that a reviewer that must approve with a digitally signature can not approve the pull request by quickly clicking on the pull request approve button
- Additional merge condition token filePathMergeChecksPass: The Workzone advanced merge condition expression can now incorporate a new condition called filePathMergeChecksPass == true. Use filePathMergeChecks to evaluate file/path reviewer quota checks explicitly. This condition comes into play if the Workzone reviewer file/path configuration has also required approvals per file/path defined.
8.3.2Bitbucket Data Center 8.0.0 - 8.11.02023-04-28Bugfix release: Mandatory file/path reviewer quota Workzone 8.3.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
8.3.2Bitbucket Server 8.0.0 - 8.11.02023-04-28Bugfix release: Mandatory file/path reviewer quota Workzone 8.3.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
8.3.1Bitbucket Data Center 8.0.0 - 8.11.02023-03-27Bugfix release: Special group names in merge condition Workzone 8.3.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
8.3.1Bitbucket Server 8.0.0 - 8.11.02023-03-27Bugfix release: Special group names in merge condition Workzone 8.3.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
8.3.0Bitbucket Data Center 8.0.0 - 8.11.02023-02-16Feature release: Configure required File/Path reviewer approval count 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.
8.3.0Bitbucket Server 8.0.0 - 8.11.02023-02-16Feature release: Configure required File/Path reviewer approval count 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.
8.2.1Bitbucket Data Center 8.0.0 - 8.11.02023-01-30Bugfix release Workzone 8.2.1 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
8.2.1Bitbucket Server 8.0.0 - 8.11.02023-01-30Bugfix release Workzone 8.2.1 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
8.2.0Bitbucket Data Center 8.0.0 - 8.11.02022-11-03Feature release: Reviewer, Signature and Merge rule order by priority 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.
8.2.0Bitbucket Server 8.0.0 - 8.11.02022-11-03Feature release: Reviewer, Signature and Merge rule order by priority 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.
8.1.0Bitbucket Data Center 8.0.0 - 8.11.02022-08-31Feature release: Quickstart and onboarding tutorials 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 ..
8.1.0Bitbucket Server 8.0.0 - 8.11.02022-08-31Feature release: Quickstart and onboarding tutorials 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 ..
8.0.0Bitbucket Data Center 8.0.0 - 8.11.02022-06-01Bitbucket 8 Only Workzone 8 is 100% compatible with Bitbucket 8.
Do not install into a Bitbucket 7 instance.
8.0.0Bitbucket Server 8.0.0 - 8.11.02022-06-01Bitbucket 8 Only Workzone 8 is 100% compatible with Bitbucket 8.
Do not install into a Bitbucket 7 instance.
7.9.1Bitbucket Data Center 7.13.0 - 7.21.122023-05-31Workflow improvements Workzone 7.9.1 features some small workflow improvements:
- When a new commit on the source branch has no effective code changes, for example after a rebase, given approvals are not withdrawn
- Workzone auto-merge diagnostics can be turned on in Workzone admin settings to log more information when an auto-merge failed.
7.9.1Bitbucket Server 7.13.0 - 7.21.122023-05-31Workflow improvements Workzone 7.9.1 features some small workflow improvements:
- When a new commit on the source branch has no effective code changes, for example after a rebase, given approvals are not withdrawn
- Workzone auto-merge diagnostics can be turned on in Workzone admin settings to log more information when an auto-merge failed.
7.9.0Bitbucket Data Center 7.13.0 - 7.21.122023-05-19Feature release - detailed merge-check veto report & secure digital signatures Workzone 7.9 is a feature release packed with goodies
- Detailed Workzone merge veto report: If Workzone vetoes a pull request merge a detailed report is accessible via the pull request page actions side bar. The merge veto report contains all details as to why the current pull request cannot be merged, including missing file/path reviewer approvals
- Additional permission checks for digital signature: additional security filter makes sure that a reviewer that must approve with a digitally signature can not approve the pull request by quickly clicking on the pull request approve button
- Additional merge condition token filePathMergeChecksPass: The Workzone advanced merge condition expression can now incorporate a new condition called filePathMergeChecksPass == true. Use filePathMergeChecks to evaluate file/path reviewer quota checks explicitly. This condition comes into play if the Workzone reviewer file/path configuration has also required approvals per file/path defined.
7.9.0Bitbucket Server 7.13.0 - 7.21.122023-05-19Feature release - detailed merge-check veto report & secure digital signatures Workzone 7.9 is a feature release packed with goodies
- Detailed Workzone merge veto report: If Workzone vetoes a pull request merge a detailed report is accessible via the pull request page actions side bar. The merge veto report contains all details as to why the current pull request cannot be merged, including missing file/path reviewer approvals
- Additional permission checks for digital signature: additional security filter makes sure that a reviewer that must approve with a digitally signature can not approve the pull request by quickly clicking on the pull request approve button
- Additional merge condition token filePathMergeChecksPass: The Workzone advanced merge condition expression can now incorporate a new condition called filePathMergeChecksPass == true. Use filePathMergeChecks to evaluate file/path reviewer quota checks explicitly. This condition comes into play if the Workzone reviewer file/path configuration has also required approvals per file/path defined.
7.8.2Bitbucket Data Center 7.13.0 - 7.21.122023-04-28Bugfix release: Mandatory file/path reviewer quota Workzone 7.8.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
7.8.2Bitbucket Server 7.13.0 - 7.21.122023-04-28Bugfix release: Mandatory file/path reviewer quota Workzone 7.8.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.
7.8.1Bitbucket Data Center 7.13.0 - 7.21.122023-03-27Bugfix release: Special group names in merge condition Workzone 7.8.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
7.8.1Bitbucket Server 7.13.0 - 7.21.122023-03-27Bugfix release: Special group names in merge condition Workzone 7.8.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.
7.8.0Bitbucket Data Center 7.13.0 - 7.21.122023-02-16Feature release: Configure required File/Path reviewer approval count 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.
7.8.0Bitbucket Server 7.13.0 - 7.21.122023-02-16Feature release: Configure required File/Path reviewer approval count 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.
7.7.2Bitbucket Data Center 7.13.0 - 7.21.122023-01-30Bugfix release Workzone 7.7.2 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
7.7.2Bitbucket Server 7.13.0 - 7.21.122023-01-30Bugfix release Workzone 7.7.2 fixes a UI problem that prevented repo configurations being decoupled from project configurations.
7.7.0Bitbucket Data Center 7.13.0 - 7.21.122022-09-29Feature release: Reviewer, Signature and Merge rule order by priority 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.
7.7.0Bitbucket Server 7.13.0 - 7.21.122022-09-29Feature release: Reviewer, Signature and Merge rule order by priority 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.
7.6.0Bitbucket Data Center 7.13.0 - 7.21.122022-08-31Feature release: Quickstart and onboarding tutorials 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 ..
7.6.0Bitbucket Server 7.13.0 - 7.21.122022-08-31Feature release: Quickstart and onboarding tutorials 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 ..
7.5.3Bitbucket Data Center 7.13.0 - 7.21.122022-05-05Minor Bugfix Release Workzone 7.5.3 fixes 2 issues with
- processing enhanced build results
- if 'ignore committer approvals' is enabled, filter out commits by committer id and not author id
7.5.3Bitbucket Server 7.13.0 - 7.21.122022-05-05Minor Bugfix Release Workzone 7.5.3 fixes 2 issues with
- processing enhanced build results
- if 'ignore committer approvals' is enabled, filter out commits by committer id and not author id
7.5.2Bitbucket Data Center 7.13.0 - 7.21.122022-03-07Bugfix release - pull request tasks Workzone 7.5.2 fixes a problem with automatic pull request merge after pull request task completion.
7.5.2Bitbucket Server 7.13.0 - 7.21.122022-03-07Bugfix release - pull request task completion Workzone 7.5.2 fixes a problem with automatic pull request merge after pull request task completion.
7.5.1Bitbucket Data Center 7.13.0 - 7.21.122022-02-24Performance improvements - processing build results Workzone 7.5.1 features performance improvements for processing incoming build results.
7.5.1Bitbucket Server 7.13.0 - 7.21.122022-02-24Performance improvements - processing build results Workzone 7.5.1 features performance improvements for processing incoming build results.
7.5.0Bitbucket Data Center 7.13.0 - 7.21.122022-02-22Feature release - partial mandatory approvals 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.
7.5.0Bitbucket Server 7.13.0 - 7.21.122022-02-22Feature release - partial mandatory approvals 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.
7.4.2Bitbucket Data Center 7.13.0 - 7.21.122021-12-16UI Bugfix release Workzone 7.4.2 fixes a UI problem with displaying reviewer configurations.
Improved Workzone swagger openapi descriptions.
7.4.2Bitbucket Server 7.13.0 - 7.21.122021-12-16UI Bugfix release Workzone 7.4.2 fixes a UI problem with displaying reviewer configurations.
Improved Workzone swagger openapi descriptions.
7.4.1Bitbucket Data Center 7.13.0 - 7.21.122021-10-29Bugfix release Workzone 7.4.1 fixes a UI problem when editing merge configurations.
Note: Workzone 7.4.1 is compatible with Bitbucket 7.13+
7.4.1Bitbucket Server 7.13.0 - 7.21.122021-10-29Bugfix release Workzone 7.4.1 fixes a UI problem when editing merge configurations.
Note: Workzone 7.4.1 is compatible with Bitbucket 7.13+
7.4.0Bitbucket Data Center 7.13.0 - 7.21.122021-10-20Repository group reviewer support 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
7.4.0Bitbucket Server 7.13.0 - 7.21.122021-10-20Repository group reviewer support 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.
7.3.3Bitbucket Data Center 7.0.0 - 7.21.122022-03-01Feature release - partial mandatory approvals 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.
7.3.3Bitbucket Server 7.0.0 - 7.21.122022-03-01Feature release - partial mandatory approvals 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.
7.3.2Bitbucket Data Center 7.0.0 - 7.13.02021-10-29Bugfix release Workzone 7.3.2 fixes a UI problem when editing merge configurations.
7.3.2Bitbucket Server 7.0.0 - 7.13.02021-10-29Bugfix release Workzone 7.3.2 fixes a UI problem when editing merge configurations.
7.3.1Bitbucket Data Center 7.0.0 - 7.21.122021-09-27UI and UX improvements, edit file and module reviewers Workzone version 7.3.1 introduces editing file and module reviewers as well as various UI and UX improvements
7.3.1Bitbucket Server 7.0.0 - 7.21.122021-09-27UI and UX improvements, edit file and module reviewers Workzone version 7.3.1 introduces editing file and module reviewers as well as various UI and UX improvements
7.3.0Bitbucket Data Center 7.0.0 - 7.21.122021-06-02Feature release - improved merge control, bugfixes 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
- Inherit global setting
- Enforce (On)
- Don’t enforce (Off)
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
7.3.0Bitbucket Server 7.0.0 - 7.21.122021-06-02Feature release - improved merge control, bugfixes 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
- Inherit global setting
- Enforce (On)
- Don’t enforce (Off)
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
7.2.5Bitbucket Data Center 7.0.0 - 7.21.122021-04-27Bugfix release Workzone 7.2.5 fixes a problem with auto-merging pull requests from repository forks.
7.2.5Bitbucket Server 7.0.0 - 7.21.122021-04-27Bugfix release Workzone 7.2.5 fixes a problem with auto-merging pull requests from repository forks.
7.2.4Bitbucket Data Center 7.0.0 - 7.21.122021-04-26Security update release Workzone 7.2.4 fixes a security vulnerability when displaying git branch names.
7.2.4Bitbucket Server 7.0.0 - 7.21.122021-04-26Security update release Workzone 7.2.4 fixes a security vulnerability when displaying git branch names.
7.2.3Bitbucket Data Center 7.0.0 - 7.21.122021-04-20Feature release - continuous integration API compatibility Workzone 7.2.3 processes build results from Bamboo and other CI systems via multiple REST API endpoints.
7.2.3Bitbucket Server 7.0.0 - 7.21.122021-04-20Feature release - continuous integration API compatibility Workzone 7.2.3 processes build results from Bamboo and other CI systems via multiple REST API endpoints.
7.2.2Bitbucket Data Center 7.0.0 - 7.21.122021-03-25Performance improvements 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 ...
7.2.2Bitbucket Server 7.0.0 - 7.21.122021-03-25Performance improvements 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 ...
7.2.1Bitbucket Data Center 7.0.0 - 7.21.122020-11-29UI Bugfix Release UI bugfix for Bitbucket 7.7+
7.2.1Bitbucket Server 7.0.0 - 7.21.122020-11-29UI Bugfix Release UI bugfix for Bitbucket 7.7+
7.2.0Bitbucket Data Center 7.0.0 - 7.21.122020-10-08Bugfix and Security release Workzone 7.2.0 improves security for REST API endpoints and fixes merge-check message content for some Workzone merge condition expressions.
7.2.0Bitbucket Server 7.0.0 - 7.21.122020-10-08Bugfix and Security release Workzone 7.2.0 improves security for REST API endpoints and fixes merge-check message content for some Workzone merge condition expressions.
7.1.0Bitbucket Data Center 7.0.0 - 7.21.122020-06-11Bugfix release Allow AD groups with '#' in their name to be used for reviewer groups and in Workzone merge conditions.
7.1.0Bitbucket Server 7.0.0 - 7.21.122020-06-11Bugfix release Allow AD groups with '#' in their name to be used for reviewer groups and in Workzone merge conditions.
7.0.0Bitbucket Data Center 7.0.0 - 7.21.122020-04-06Bitbucket 7.x compatibility release. Workzone 7.0 is a Bitbucket 7.x compatibility release.
7.0.0Bitbucket Server 7.0.0 - 7.21.122020-04-06Bitbucket 7.x compatibility release. Workzone 7.0 is a Bitbucket 7.x compatibility release.
6.7.2Bitbucket Data Center 6.0.0 - 6.10.172022-02-18Feature release - partial mandatory approvals 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.
6.7.2Bitbucket Server 6.0.0 - 6.10.172022-02-18Feature release - partial mandatory approvals 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.
6.6.1Bitbucket Data Center 6.0.0 - 6.10.172021-09-27UI and UX improvements, edit file and module reviewers Workzone version 6.6.1 introduces editing file and module reviewers as well as various UI and UX improvements
6.6.1Bitbucket Server 6.0.0 - 6.10.172021-09-27UI and UX improvements, edit file and module reviewers Workzone version 6.6.1 introduces editing file and module reviewers as well as various UI and UX improvements
6.6.0Bitbucket Data Center 6.0.1 - 6.10.172021-06-02Feature release - improved merge control, bugfixes 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
- Inherit global setting
- Enforce (On)
- Don’t enforce (Off)
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
6.6.0Bitbucket Server 6.0.1 - 6.10.172021-06-02Feature release - improved merge control, bugfixes 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
- Inherit global setting
- Enforce (On)
- Don’t enforce (Off)
Workzone 7.3.0 also fixes a problem when a mandatory reviewer configuration was added after a pull request was created.
6.5.6Bitbucket Data Center 6.0.0 - 6.10.172021-04-28Bugfix release Workzone 6.5.6 fixes a problem with auto-merging pull requests from repository forks.
6.5.6Bitbucket Server 6.0.0 - 6.10.172021-04-28Bugfix release Workzone 6.5.6 fixes a problem with auto-merging pull requests from repository forks.
6.5.5Bitbucket Data Center 6.0.0 - 6.10.172021-04-26Security update release Workzone 6.5.5 fixes a security vulnerability when displaying git branch names.
6.5.5Bitbucket Server 6.0.0 - 6.10.172021-04-26Security update release Workzone 6.5.5 fixes a security vulnerability when displaying git branch names.
6.5.3Bitbucket Data Center 6.0.0 - 6.10.172021-03-25Performance improvements 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 ...
6.5.3Bitbucket Server 6.0.0 - 6.10.172021-03-25Performance improvements 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 ...
6.5.2Bitbucket Data Center 6.0.0 - 6.10.172020-10-12Performance improvements 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.
6.5.2Bitbucket Server 6.0.0 - 6.10.172020-10-12Performance improvements 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.
6.5.1Bitbucket Data Center 6.0.0 - 6.10.172020-10-06Bugfix release Workzone 6.5.1 fixes a problem with pull request approval digital signatures.
6.5.1Bitbucket Server 6.0.0 - 6.10.172020-10-06Bufix release 6.5.0Bitbucket Data Center 6.0.0 - 6.10.172020-10-05Security release Workzone 6.5.0 improves app related REST API security.
6.5.0Bitbucket Server 6.0.0 - 6.10.172020-10-05Security release Workzone 6.5.0 improves app related REST API security.
6.4.1Bitbucket Data Center 6.0.0 - 6.10.172020-04-25Bugfix Release Workzone 6.4.1 fixes a problem with workzone group quotas for group names with hash (#)
6.4.1Bitbucket Server 6.0.0 - 6.10.172020-04-25Bugfix Release Workzone 6.4.1 fixes a problem with workzone group quotas for group names with hash (#)
6.4.0Bitbucket Data Center 6.0.0 - 6.10.172020-04-17Bugfix Release Workzone 6.4 improves the way mandatory file path reviewers and groups are added to pull requests.
6.4.0Bitbucket Server 6.0.0 - 6.10.172020-04-17Bugfix Release Workzone 6.4 improves the way mandatory file path reviewers and groups are added to pull requests.
6.3.1Bitbucket Data Center 6.0.0 - 6.10.172019-10-15Feature Release - reviewer approval count merge check 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.
6.3.1Bitbucket Server 6.0.0 - 6.10.172019-10-15Feature Release - reviewer approval count merge check 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.
6.2.1Bitbucket Data Center 6.0.0 - 6.10.172019-09-08Bugfix Release - UI Version 6.2.1 fixes a UI problem when resetting Workzone repository properties (hooks) to Workzone project properties settings.
6.2.1Bitbucket Server 6.0.0 - 6.10.172019-09-08Bugfix Release - UI Version 6.2.1 fixes a UI problem when resetting Workzone repository properties (hooks) to Workzone project properties settings.
6.2.0Bitbucket Data Center 6.0.0 - 6.10.172019-08-05Feature Release - Include and exclude file paths for reviewers Refined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
- include pattern src/main/test**
6.2.0Bitbucket Server 6.0.0 - 6.10.172019-08-05Feature Release - Include and exclude file paths for reviewers Refined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
- include pattern src/main/test**
6.1.2Bitbucket Data Center 6.0.0 - 6.10.172019-07-03Bugfix Release Workzone 6.1.2 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
6.1.2Bitbucket Server 6.0.0 - 6.10.172019-07-03Bugfix Release Workzone 6.1.2 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
6.1.1Bitbucket Data Center 6.0.0 - 6.10.172019-06-12Bugfix Release Release Workzone 6.1.1 now recognizes AD group names with whitespace like 'Test Group 1'
6.1.1Bitbucket Server 6.0.0 - 6.10.172019-06-12Bugfix Release Workzone 6.1.1 now recognizes AD group names with whitespace like 'Test Group 1'
6.1.0Bitbucket Data Center 6.0.0 - 6.10.172019-05-12Feature Release - Workzone audit logging configuration Workzone 6.1.0 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
6.1.0Bitbucket Server 6.0.0 - 6.10.172019-05-12Feature Release - Workzone audit logging configuration Workzone 6.1.0 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
6.0.2Bitbucket Data Center 6.0.0 - 6.10.172019-04-17Bugfix Release Fixes an Internet Exploder 11 JS problem
6.0.2Bitbucket Server 6.0.0 - 6.10.172019-04-17Bugfix Release Fixes Internet Exploder 11 JS problem
6.0.1Bitbucket Data Center 6.0.0 - 6.10.172019-03-23Bugfix Release Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
6.0.1Bitbucket Server 6.0.0 - 6.10.172019-03-23Bugfix Release Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
6.0.0Bitbucket Data Center 6.0.0 - 6.10.172019-03-07Bitbucket 6, UI Improvements Workzone 6.0 is fully compatible with Bitbucket 6.
6.0.0Bitbucket Server 6.0.0 - 6.10.172019-03-07Bitbucket 6, UI Improvements Workzone 6.0 is fully Bitbucket 6 compatible.
Minor UI changes and improvements for compatibility.
5.11.2Bitbucket Data Center 5.9.0 - 5.16.112021-04-26Security update release Version 5.11.2 • Released 2021-04-26 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 5.11.2 fixes a security vulnerability when displaying git branch names.
5.11.2Bitbucket Server 5.9.0 - 5.16.112021-04-26Security update release Version 5.11.2 • Released 2021-04-26 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 5.11.2 fixes a security vulnerability when displaying git branch names.
5.11.1Bitbucket Data Center 5.9.0 - 5.16.112021-03-25Performance improvements Version 5.11.1 • Released 2021-03-25 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 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 ...
5.11.1Bitbucket Server 5.9.0 - 5.16.112021-03-25Performance improvements Version 5.11.1 • Released 2021-03-25 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 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 ...
5.11.0Bitbucket Data Center 5.9.0 - 5.16.112019-10-10Feature Release - Approval Counts Version 5.11.0 • Released 2019-10-10 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 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.
5.11.0Bitbucket Server 5.9.0 - 5.16.112019-10-10Feature Release - Approval Counts Version 5.11.0 • Released 2019-10-10 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialWorkzone 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.
5.10.1Bitbucket Data Center 5.9.0 - 5.16.112019-08-05Feature Release - Include and exclude file paths for reviewers Version 5.10.1 • Released 2019-08-05 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialRefined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
- include pattern src/main/test**
5.10.1Bitbucket Server 5.9.0 - 5.16.112019-08-05Feature Release - Include and exclude file paths for reviewers Version 5.10.1 • Released 2019-08-05 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialRefined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files by configuring
- include pattern src/main/test**
5.10.0Bitbucket Data Center 5.9.0 - 5.16.112019-08-04Feature Release - Include and exclude file paths for reviewers Version 5.10.0 • Released 2019-08-04 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialRefined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files.
5.10.0Bitbucket Server 5.9.0 - 5.16.112019-08-04Feature Release - Include and exclude file paths for reviewers Version 5.10.0 • Released 2019-08-04 • Supported By Izymes Pty Ltd • Paid via Atlassian • CommercialRefined configuration of reviewers for files and modules:
- include patterns like src/main/**
- exclude patterns like src/main/test**
Your development team/group reviews all files except src/main/test.
The test team reviews test files.
5.9.4Bitbucket Data Center 5.9.0 - 5.16.112019-07-01Bugfix Release Workzone 5.9.4 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
5.9.4Bitbucket Server 5.9.0 - 5.16.112019-07-01Bugfix Release Workzone 5.9.4 fixes a bug with e-signatures - only the logged in user can sign a PR approval.
5.9.3Bitbucket Data Center 5.9.0 - 5.16.112019-06-12Bugfix Release Workzone 5.9.3 now recognizes AD group names with whitespace like 'Test Group 1' .
5.9.3Bitbucket Server 5.9.0 - 5.16.112019-06-12Bugfix Release Workzone 5.9.3 recognises whitespace in AD group names like 'Test Group 1'
5.9.2Bitbucket Data Center 5.9.0 - 5.16.112019-05-16Bugfix Release 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.
5.9.2Bitbucket Server 5.9.0 - 5.16.112019-05-16Bugfix Release 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.
5.9.1Bitbucket Data Center 5.9.0 - 5.16.112019-05-08Feature release - Workzone audit logging configuration Workzone 5.9.1 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
5.9.1Bitbucket Server 5.9.0 - 5.16.112019-05-08Feeature release - Workzone audit logging configuration Workzone 5.9.1 features the ability to configure Workzone config change audit logging priority in Workzone global settings.
5.9.0Bitbucket Data Center 5.9.0 - 5.16.112019-04-26Feature Release - Workzone config audit logging Workzone 5.9.0 introduces configuration change audit logging for
- Global Workzone config changes
- Workzone project config changes
- Workzone repository config changes
All events are published with HIGH audit logging priority.
5.9.0Bitbucket Server 5.9.0 - 5.16.112019-04-26Feature Release - Workzone config audit logging Workzone 5.9.0 introduces configuration change audit logging for
- Global Workzone config changes
- Workzone project config changes
- Workzone repository config changes
All events are published with HIGH audit logging priority.
5.8.3Bitbucket Data Center 5.9.0 - 5.16.112019-03-23Bugfix Release Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
5.8.3Bitbucket Server 5.9.0 - 5.16.112019-03-23Bugfix Release Workzone 5.8.3 fixes a problem when decoupling and copying project settings into repository settings.
5.8.2Bitbucket Data Center 5.9.0 - 5.16.112019-02-11Minor UI Bugfix Workzone version 5.8.2 fixes a problem with toggles in Safari and Edge browsers
5.8.2Bitbucket Server 5.9.0 - 5.16.112019-02-11Minor UI Bugfix Version 5.8.2 fixes a problem with toggles in Edge and Safari browsers
5.8.1Bitbucket Data Center 5.9.0 - 5.16.112019-01-06Performance and UI Improvements 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.
5.8.1Bitbucket Server 5.9.0 - 5.16.112019-01-06Performance and UI Improvements 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.
5.8.0Bitbucket Data Center 5.9.0 - 5.16.112019-01-01Server and Data Center Release Workzone 5.8.0 is officially approved by Atlassian for
- Bitbucket Data Center
- Bitbucket Server
5.7.1Bitbucket Server 5.9.0 - 5.16.112018-12-16Bugfix Release 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 ==
5.7.0Bitbucket Server 5.9.0 - 5.16.112018-09-12Feature Release - Needs Work Veto and Watch Task Completion Workzone 5.7 proudly introduces
- Configure 'Needs work' veto on global, project and repository level. Block Pull Request (auto) merge if a PR is marked with 'needs work'
- Watch Task Completion events. Pull requests can now be auto-merged when a PR task is completed.
Note: Workzone 5.7 is Datacenter compatible (as you would expect)
5.6.3Bitbucket Server 5.2.0 - 5.16.112018-08-20Bugfix Release Version 5.6.3 fixes a Workzone auto-merge bug with mandatory reviewers are part of the pull request reviewers set.
5.6.2Bitbucket Server 5.2.0 - 5.13.02018-04-26Bugfix Release Workzone version 5.6.2 improves auto-merge when watching incoming (successful) build results.
5.6.1Bitbucket Server 5.2.0 - 5.13.02018-04-21Minor UI Improvements The release improves the merge-veto message content shown when pull requests can't be merged due to Workzone merge-conditions not being met.
5.6.0Bitbucket Server 5.2.0 - 5.13.02018-02-07Merge condition feature and UI improvements Version 5.6.0 of Workzone features a new merge condition element
- Ignore contributor approvals for pull requests. Workzone will not count approvals from users that directly committed code for the pull request
Workzone now also has an improved (auto)-merge configuration UI.
5.5.0Bitbucket Server 5.2.0 - 5.13.02017-12-20Workzone PROJECT settings 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.
5.4.0Bitbucket Server 5.0.2 - 5.13.02017-12-04Bugfix Release - Group membership 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.
5.3.2Bitbucket Server 5.0.2 - 5.13.02017-09-27Releasing 5.3.1 as .JAR file Same as version 5.3.1 - but this release artifact contains the Workzone JAR file
5.3.1Bitbucket Server 5.0.2 - 5.13.02017-09-27Important bugfix release 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.
5.3.0Bitbucket Server 5.0.2 - 5.13.02017-08-29Feature and Bugfix Release Workzone 5.0.3 features
- Configurable merge strategy for automatic merges, inherit from repository settings or configure branch specific merge strategy
Bugfixes
- REST API returns populated default workflow properties
- Fixes a PR rescope notification bug
5.2.0Bitbucket Server 5.0.2 - 5.13.02017-08-06Feature Release: 'Needs work' on pull request can block merge - 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
5.1.0Bitbucket Server 5.0.0 - 5.13.02017-07-11Merge condition with specific named group quota - for Bitbucket 5 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 ...
5.0.1Bitbucket Server 5.0.0 - 5.13.02017-05-26Bitbucket 5.0 Compatibility Workzone 5.0.1 provides compatibility with Bitbucket Server 5
4.6.4Bitbucket Server 4.4.0 - 4.14.122018-05-16Feature and Bugfix Release 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.
4.6.2Bitbucket Server 4.4.0 - 4.14.122017-12-18Performance Improvements Version 4.6.2 features some performance improvements for Workzone's CI server integration (Bamboo, Jenkins etc) when processing large amounts of build results.
4.6.0Bitbucket Server 4.4.0 - 4.14.122017-08-06Feature Release: 'Needs work' on pull request can block merge * 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
4.5.1Bitbucket Server 4.3.0 - 4.14.122017-07-03Merge condition with specific named group quota 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 ...
4.4.4Bitbucket Server 4.0.0 - 4.14.122017-05-16Bugfix Release TLDR;
Workzone version 4.4.4 fixes a digital signature approval problem.
The nitty-gritty:
- When approvals that require digital signatures are defined via groups and the (auto-)merge condition has a group quota
- Then group membership of the signature-approvers needs to be considered when counting approvals towards the required groupQuota
4.4.3Bitbucket Server 4.0.0 - 4.14.122017-02-28Performance Improvements Workzone 4.4.3 aims at performance improvements when detecting potential merge conflicts.
4.4.2Bitbucket Server 4.0.0 - 4.14.122016-11-14File / Directory updates to pull request consider configured reviewers When a PR is updated (rescoped) with new files, all reviewers responsible for these directories/files are also added to the PR.
4.4.0Bitbucket Server 4.0.0 - 4.14.122016-11-07File / Directory reviewers for pull requests Workzone 4.4.0 features file and directory pull request reviewers. Watch it in action
- Configure multiple file/path patterns like 'src/**/*.java' to add reviewers or groups by file or directory path
- Distribute review and approval responsibilities among your team by assigning designated reviewers for packages, directories or files.
- Extend existing branch reviewer configurations with file and directory based reviewers
4.3.4Bitbucket Server 4.0.0 - 4.14.122016-10-22Bugfix Release Fixes for
- After removing a reviewer from a pull request Workzone tries to merge the pull request twice
4.3.3Bitbucket Server 4.0.0 - 4.14.122016-08-31Bugfix Release 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.
4.3.2Bitbucket Server 4.0.0 - 4.14.122016-07-05Feature Release : Disable Auto-Merge but keep merge conditions 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.
4.3.0Bitbucket Server 4.0.0 - 4.14.122016-06-20Improve Pull Requests Digital Signature UI This release features
- A light revamp of the Pull Requests digital signatures UI
- Minor bugfixes and improvements based on constructive customer feedback
4.2.4Bitbucket Server 4.0.0 - 4.14.122016-05-11Bugfix Release 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.
4.2.3Bitbucket Server 4.0.0 - 4.6.02016-05-02Bugfix Release - send merge conflict notifications only if the conflict is caused by a PR target ref change (i.e. a conflict caused by a merge from a different source branch)
4.2.2Bitbucket Server 4.0.0 - 4.6.02016-04-12Bugfix Release Workzone 4.2.2 is a minor bugfix release
- Reviewers and Approvers configuration UI improvements.
4.2.1Bitbucket Server 4.0.0 - 4.6.02016-03-23Digital Signatures UI Improvements This release features some minor UI improvements around digital signatures for Pull Request approvals.
4.2.0Bitbucket Server 4.0.0 - 4.6.02016-03-01Approve Pull Requests with a Digital Signature. CFR Part 11 Compliance. Digitally Signed Approvals
- CFR Part 11 compliance with digitally signed Pull Request Approvals
- Signees must approve with their username and password.
- Require N digital signatures before a Pull Request can be merged
- Track signed off Pull Requests
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.
4.6.3Bitbucket Server 4.4.0 - 4.14.122018-05-12Feature Release 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.
4.6.1Bitbucket Server 4.4.0 - 4.14.122017-12-18Performance Improvements Version 4.6.1 features some performance improvements for Workzone's CI server (Bamboo, Jenkins etc) integration when processing large amounts of build results.
4.1.2Bitbucket Server 4.0.0 - 4.6.02015-12-04Bugfix Release Minor UI bugfix - saving reviewer configuration source branch correctly. Thanks to Sylvia Yee for reporting this bug.
4.1.1Bitbucket Server 4.0.0 - 4.6.02015-11-01Publish Workzone Configurations to other Projects Release 4.1.1 adds the long awaited feature to publish / bulk change Workzone repository settings to other project's repositories.
- Publish reviewer configuration
- Publish auto-merge configuration
- Publish workflow configuration
- Publish all repository configurations at once
'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.
4.1.0Bitbucket Server 4.0.0 - 4.6.02015-11-01Publish Workzone Configurations to Projects Release 4.1.0 adds the long awaited feature to publish / bulk change Workzone repository settings to other project's repositories.
- Publish reviewer configuration
- Publish auto-merge configuration
- Publish workflow configuration
- Publish all repository configurations at once
'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.
4.0.1Bitbucket Server 4.0.0 - 4.6.02015-10-27UI Bugfix Release This bug fix release addresses a problem when adding a reviewer configuration with ref (branch) patterns.
4.0.0Bitbucket Server 4.0.0 - 4.6.02015-09-22Bitbucket Server Release Version 4.0.0 of Workzone is compatible with Bitbucket Server 4.0.0.
Please do not use Workzone 4.0.0 for Stash.
3.1.5Bitbucket Server 3.5.0 - 3.11.62016-05-11Bugfix Release 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.
3.1.3Bitbucket Server 3.5.0 - 3.11.62016-05-01Bugfix Release for Stash 3.x Workzone 3.1.3 is a bugfix release for Stash 3.5 - 3.11.
- Send merge conflict notification only when the conflict was caused by a change in the target branch
3.1.2Bitbucket Server 3.5.0 - 3.11.62015-09-15Bugfix Release Support mixed case group names. Special thanks to J.T. Conklin (Dell) for all the support.
3.1.1Bitbucket Server 3.5.0 - 3.11.62015-09-06Bugfix Release 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.
3.1.0Bitbucket Server 3.5.0 - 3.11.62015-08-27Auto-merge Improvements This release includes a new Pull Request auto-merge feature.
- Workzone attempts to merge Pull Requests that don't have any reviewers yet and that are not subject to reviewers being added by Workzone (no matching reviewer configuration defined).
- Immediate auto-merge is disabled by default and can be enabled in Workzone's global configuration
- Immediate auto-merge is helpful in case Pull Requests don't need user approval but may depend on successful build results.
3.0.0Bitbucket Server 3.5.0 - 3.11.62015-08-10Major Feature Release - Complex Merge Conditions Workzone 3.0 is a major release featuring auto-merge conditions extensions
- Per-group Approval Quota (N users per specified reviewer group must approve)
- Required Build Results per _Branch_
- Auto-merge conditions built from Boolean Expressions like requiredBuildsCount > 1 & ( approvalQuota >= 50% | groupQuota >= 2 )
- Free form merge-condition builder.
For a quick intro watch the tutorial.
2.4.7Bitbucket Server 3.2.0 - 3.11.62015-07-15Bugfix Release 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)
2.4.6Bitbucket Server 3.2.0 - 3.11.62015-06-17Bugifx Release Version 2.4.6 fixes a branch-deletion problem after auto-merge with Stash 3.10.
- For Stash 3.10 temporary escalated repo write-permissions must be used to trigger source branch deletion after a successful merge (if configured in Workzone's auto-merge setup)
2.4.5Bitbucket Server 3.2.0 - 3.11.62015-06-03Performance Improvements This release contains several performance improvements w.r.t.
- Pull request related events (Creation, Approvals, Updates)
- Incoming Build result processing
2.4.4Bitbucket Server 3.2.0 - 3.11.62015-05-17Configure Number of Reviewers per Group This is a feature release enables admins to set the limit of reviewers per reviewer group.
- Globally configure a limit of how many users per group can be added by Workzone as reviewers.
- Default is 20.
- Larger enterprises may set a higher figure to add more users for each reviewer group.
This release also enforces license checks when reviewers are added to new Pull Requests and when attempting to merge Pull Requests automatically.
2.4.3Bitbucket Server 3.2.0 - 3.11.62015-04-29Bugfix Release This minor bug fix release improves incoming CI server build status processing.
2.4.2Bitbucket Server 3.2.0 - 3.11.62015-04-14Bugfix and Stash 3.8 Compatibility Bugfixes for
Fix for undocumented and un-announced Stash 3.8 email template removals.
2.4.1Bitbucket Server 3.2.0 - 3.11.62015-04-01Performance Improvements 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.
2.4.0Bitbucket Server 3.2.0 - 3.11.62015-03-10Major Feature Release - Conditional PR Merge Veto This is a major feature release introducing three new Workzone global configurations for
- Finally and with lots of votes behind: Disable Workzone notifications after adding reviewers automatically to new Pull Requests
- Enable conditional Pull Request merge veto (block) based on Workzone's Pull Request merge conditions. Avoid accidental or intentional pre-mature merging of Pull Requests by blocking the merge button when the configured merge conditions are not met.
- Allow user feedback to @workzone_ via twitter and help improve
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.
2.3.2Bitbucket Server 3.2.0 - 3.11.62015-02-22Bugfix Release This is a CI (Build System/Bamboo) integration bug fix release.
- Workzone can now auto-merge on successful build from CI servers that are connected via OAuth (App-links).
2.3.1Bitbucket Server 3.0.1 - 3.11.62015-02-12Bugfix Release Ability to set/edit auto merge quota parameter.
2.3.0Bitbucket Server 3.0.1 - 3.11.62015-02-03Let Workzone Suggest and Add Top Committers as Reviewers 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.
- Configure how many of the recent top committers should be added as suggested reviewers
- Configure how far back in the history Workzone should detect top committers
Check out the release notes and the documentation for more details.