Minor version update

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.

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.

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.

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.

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.

Read more

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.

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.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.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.

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.

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.

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.

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

• processing enhanced build results
• if 'ignore committer approvals' is enabled, filter out commits by committer id and not author id

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

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

• 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.

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.

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

• 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.

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.

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.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.

Release Notes

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.

Release Notes

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:

• 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**

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**

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:

• 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**

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**

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.

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.

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

• Global Workzone config changes
• Workzone project config changes
• Workzone repository config changes

All events are published with HIGH audit logging priority.

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.

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

• Bitbucket Data Center
• Bitbucket Server

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

• 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)

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

• 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.

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.

Read all about it!

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

• 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

• 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 ...

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:

• 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

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

• 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

Fixes for

• After removing a reviewer from a pull request Workzone tries to merge the pull request twice

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

• A light revamp of the Pull Requests digital signatures UI
• Minor bugfixes and improvements based on constructive customer feedback

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.

• 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)

Workzone 4.2.2 is a minor bugfix release

• Reviewers and Approvers configuration UI improvements.

This release features some minor UI improvements around digital signatures for Pull Request approvals.

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.