Support & Downloads

Izymes builds easy-to-use apps for Atlassian applications that boost your productivity, free you from performing repetitive tasks inside Confluence, Jira and Bitbucket and enable you to use your time for what you do best – YOUR job.

Book a Demo

Interested in a 1-on-1 demonstration of Izymes’s products?
Here we will walk you through;

• All features and benefits of the product you are interested in trying.
• How to set up the account and configure the settings.
• Other tips, tricks and best practices.

It will also give us time to answer any questions you may have, or perhaps you just want to have a chat, we love a good chat.
You can schedule a time on the Calendly link below. Talk soon!

Contact Info
HQ Southport
Queensland, Australia
[email protected]
Follow Us
View Categories

Release Notes (Server / Data Center)

9 min read

Version 9 #

Version 9.1.0 • Released 2024-11-04

Workzone 9.1.0 adds a repository hook to optionally revoke pull request approvals on _any_ source branch commit, even if it was a rebase without code changes.

Additionally Workzone 9.1.0 features workflow optimizations: Contextual un-approve on pull request update. When a pull request is updated, only affected file/path reviewer approvals are revoked, not all approvals. Requires file/path reviewer configuration.

This version also fixes a bug where approvals are revoked when the pull request source branch was synchronized with the destination branch, although the effective diff of the pull request has not changed.

Version 9.0.0 • Released 2024-07-26

Workzone 9 is a compatibility release for Bitbucket 9 platform release.

There are no functionality, API or UI changes.

Version 8 #

Version 8.6.0 • Released 2024-11-04

Workzone 8.6.0 adds a repository hook to optionally revoke pull request approvals on _any_ source branch commit, even if it was a rebase without code changes.

Additionally Workzone 8.6.0 features workflow optimizations: Contextual un-approve on pull request update. When a pull request is updated, only affected file/path reviewer approvals are revoked, not all approvals. Requires file/path reviewer configuration.

This version also fixes a bug where approvals are revoked when the pull request source branch was synchronized with the destination branch, although the effective diff of the pull request has not changed.

Version 8.5.0 • Released 2024-10-21

Workzone 8.5.0 adds a repository hook to optionally revoke pull request approvals on _any_ source branch commit, even if it was a rebase without code changes.

This version also fixes a bug where approvals are revoked when the pull request source branch was synchronized with the destination branch, although the effective diff of the pull request has not changed.

Version 8.4.0 • Released 2023-05-23

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.

Version 8.3.2 • Released 2023-04-28

Workzone 8.3.2 fixes a bug for mandatory file/path reviewer quota evaluation in combination with other merge conditions.

Version 8.3.1 • Released 2023-03-27

Workzone 8.3.1 fixes a problem with special (though valid) characters in group names for advanced merge conditions.

Version 8.3.0 • Released 2023-02-16

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.

Version 8.2.1 • Released 2023-01-30

Workzone 8.2.1 fixes a UI problem that prevented repo configurations being decoupled from project configurations.

Version 8.2.0 • Released 2022-11-03

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

Version 8.1.0 • Released 2022-08-31

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

Version 8.0.0 • Released 2022-06-01

Workzone 8 is 100% compatible with Bitbucket 8.

Do not install into a Bitbucket 7 instance.

Version 7 #

Version 7.7.0 • Released 2022-09-29

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…

Version 7.6.0 • Released 2022-08-31

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

Version 7.5.3 • Released 2022-05-05

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

Version 7.5.2 • Released 2022-03-07

Workzone 7.5.2 fixes a problem with automatic pull request merge after pull request task completion.

Version 7.5.1 • Released 2022-02-24

Workzone 7.5.1 features performance improvements for processing incoming build results.

Version 7.5.0 • Released 2022-02-22

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.

Version 7.4.2 • Released 2021-12-16

Workzone 7.4.2 fixes a UI problem with displaying reviewer configurations.

Improved Workzone swagger openapi descriptions.

Version 7.4.1 • Released 2021-10-29

Workzone 7.4.1 fixes a UI problem when editing merge configurations.

Note: Workzone 7.4.1 is compatible with Bitbucket 7.13+

Version 7.4.0 • Released 2021-10-20

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

Version 7.3.3 • Released 2022-03-01

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.

Version 7.3.2 • Released 2021-10-29

Workzone 7.3.2 fixes a UI problem when editing merge configurations.

Version 7.3.1 • Released 2021-09-27

Workzone version 7.3.1 introduces editing file and module reviewers as well as various UI and UX improvements

Version 7.3.0 • Released 2021-06-02

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.

Version 7.2.5 • Released 2021-04-27

Workzone 7.2.5 fixes a problem with auto-merging pull requests from repository forks.

Version 7.2.4 • Released 2021-04-26

Workzone 7.2.4 fixes a security vulnerability when displaying git branch names.

Version 7.2.3 • Released 2021-04-20

Workzone 7.2.3 processes build results from Bamboo and other CI systems via multiple REST API endpoints.

Version 7.2.2 • Released 2021-03-25

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 …

Version 7.2.1 • Released 2020-11-29

UI bugfix for Bitbucket 7.7+

Version 7.2.0 • Released 2020-10-08

Workzone 7.2.0 improves security for REST API endpoints and fixes merge-check message content for some Workzone merge condition expressions.

Version 7.1.0 • Released 2020-06-11

Allow AD groups with ‘#’ in their name to be used for reviewer groups and in Workzone merge conditions.

Version 7.0.0 • Released 2020-04-06

Workzone 7.0 is a Bitbucket 7.x compatibility release.

Version 6 #

Version 6.7.2 • Released 2022-02-18

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.

Version 6.6.1 • Released 2021-09-27

Workzone version 6.6.1 introduces editing file and module reviewers as well as various UI and UX improvements

Version 6.6.0 • Released 2021-06-02

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.

Version 6.5.6 • Released 2021-04-28

Workzone 6.5.6 fixes a problem with auto-merging pull requests from repository forks.

Version 6.5.5 • Released 2021-04-26

Workzone 6.5.5 fixes a security vulnerability when displaying git branch names.

Version 6.5.3 • Released 2021-03-25

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 …

Version 6.5.2 • Released 2020-10-12

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.

Version 6.5.1 • Released 2020-10-06

Workzone 6.5.1 fixes a problem with pull request approval digital signatures.

Version 6.5.0 • Released 2020-10-05

Workzone 6.5.0 improves app related REST API security.

Version 6.4.1 • Released 2020-04-25

Workzone 6.4.1 fixes a problem with workzone group quotas for group names with hash (#)

Version 6.4.0 • Released 2020-04-17

Workzone 6.4 improves the way mandatory file path reviewers and groups are added to pull requests.

Try Workzone!