Control Freak - Commit Checks and Jira Hooks for Bitbucket

Version v2025.11.18 contains two enhancements and one important fix:

2 enhancements:

1.) We now bundle a “control-freak-sbom.json” SBOM file in the root of every release.

2.) We have added a whitelist for the file blocking logic. Files that match the whitelist will be allowed through (they will not be blocked).

1 important fix:

There was a regression in v2025.11.17 that allowed all large files to be pushed even if the large file limit was set.

DO NOT USE THIS RELEASE - it has a bug with large file blocking that is fixed in version v2025.11.18

Version v2025.11.17 contains two enhancements:

1.) We now bundle a “control-freak-sbom.json” SBOM file in the root of every release.

2.) We have added a whitelist for the file blocking logic. Files that match the whitelist will be allowed through (they will not be blocked).

Version v2025.09.26-bb10 contains 1 fix:

1.) This is the “Bitbucket 10.x” compatible version of v2025.09.26.

Version v2025.09.26 contains 1 fix:

1.) Oops, regression: broke is-fast-forward in previous for history rewrites.

Version v2025.09.24-bb10 contains 1 fix:

1.) This is the “Bitbucket 10.x” compatible version of v2025.09.24.

Version v2025.09.24 contains 2 fixes:

1.) The “is this a fast-forward merge” logic did not consider forks. Fixed!

2.) Small error-handling bug fixed. The “is this a fast-forward merge” logic was not handling any possible git errors correctly.

Version v2025.09.23 contains 1 fix:

1.) Small error-handling bug fixed. The “is this a fast-forward merge” logic was not handling any possible git errors correctly.

Version v2025.08.30 contains 1 important fix:

1.) Since v2025.08.01 we’ve been trying to handle the Jira JQL search deprecation (see: https://developer.atlassian.com/changelog/#CHANGE-2046 ). We recently discovered the “/rest/api/2/serverInfo” endpoint, and this endpoint doesn’t require any authentication, so we think it should finally work for all Control Freak deployments. To see that endpoint for yourself: https://bit-booster.atlassian.net/rest/api/2/serverInfo ! :-)

Background: the Jira DC and Jira Cloud rest endpoints for doing JQL queries no longer behave identically, so Control-Freak needs to figure out which type of Jira it's talking to before it builds up its JQL request. And we can’t just look at the Jira URL (e.g., my-company.atlassian.net), because some companies customize Jira Cloud to use their own domain (e.g., jira.my-company.com).

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Version v2025.08.29 contains 1 important fix:

1.) Since v2025.08.1 we’ve been trying to handle the Jira JQL search deprecation (see: https://developer.atlassian.com/changelog/#CHANGE-2046 ). We recently discovered the “/rest/api/2/serverInfo” endpoint, and this endpoint doesn’t require any authentication, so we think it should finally work for all Control Freak deployments. To see that endpoint for yourself: https://bit-booster.atlassian.net/rest/api/2/serverInfo ! :-)

Background: the Jira DC and Jira Cloud rest endpoints for doing JQL queries no longer behave identically, so Control-Freak needs to figure out which type of Jira it's talking to before it builds up its JQL request. And you can’t just look at the Jira URL (e.g., my-company.atlassian.net), because some companies customize that to use their own domain (e.g., jira.my-company.com).

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Version v2025.08.22 contains 1 important fix:

1.) Fix the regression introduced in v2025.08.01. It would block pushes and complain that the OAUTH connection was missing even though it was fine (but this problem only occurred when Jira-Impersonation was enabled in the Control-Freak config).

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Version v2025.08.01 contains 2 important fixes:

1.) Handle Jira Cloud “/search” REST deprecation - https://developer.atlassian.com/changelog/#CHANGE-2046. If you’re using Bitbucket DC + Jira Cloud, this is an important fix!

2.) Based on Atlassian guidance, remove @ExportAsService annotation from all classes (especially Servlets) except for the one class where it's necessary (ControlFreakOnStart.java).

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Another tiny improvement to error reporting logic. In particular if the Bitbucket to Jira username mapping cannot be resolved, instead of blowing up with a NPE in that case, we now print something like: Queried Jira as Bitbucket user [julius@bit-booster.com] and Jira user [UNKNOWN].

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Small improvement to error reporting logic.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

Control-Freak version v2025.05.06 contains some performance improvements to reduce the resource usage of “git” commands Control-Freak invokes when it analyses each push and/or merge.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

2 fixes:

• Bugfix: Jira-policy was blocking new-branch-creation inappropriately when the “[x] - All Others” checkbox was checked. In addition, the grandfathering logic was not quite right.

• Bugfix: Global Settings pages should be available (not read-only) even when Control-Freak does not have a valid commercial license in place.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

5 fixes:

• REST endpoint now offered via /rest/control-freak/1.0/config/${project}/${repo} (note: old REST api location still works, but doesn’t work with HTTP access tokens since Bitbucket versions 8.9.22 or newer, 8.19.12 or newer, and 9.3.2 or newer).

• Branch-name-must-match-Jira now only checks LAST jira ref in branch name.
• commit-message-length control fixed - now applies to all new pushes, and grandfathers older commits correctly.
• Two enhancements:

a.) commit-message-title-length control
b.) look for FIRST Jira ref only option

- - - - -

Since v2024.07.28, Control-Freak is now a paid app. More information here: https://bit-booster.com/licensing-change/

We have made adjustments to the "git log" command that Control-Freak uses to retrieve commit metadata. These adjustments have significantly improved Control-Freak's performance (e.g., we saw typical scenarios go from 1.333s down to 0.050s).

The bulk of the gains came from removing "--date-order" as well as switching to "-m --name-only" instead of "-c --name-only" when checking for submodule updates.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

Pushes could be erroneously blocked by the "no-rewrites" rule if they contained more than 333 commits.

Merges could be erroneously blocked by the "fast-forward-only" rule if they contained more than 333 commits.

Fixed! There is now no limit on the number of commits: even a fast-forward merge or push with 50,000+ commits will be correctly accepted under these two scenarios.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

One important bug fix: unfortunately we introduced a regression in v2024.07.10 related to our Jira grandfathering logic. This logic is important because it allows merges between "Jira policy enabled" branches even after the Jira tickets have been marked "Closed".

- - - - -

Since v2024.07.28, Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

One bug fix and two enhancements

Bug fix:

• Deleting non-existent branches via "git push" with Control-Freak enabled causes a very large and intimidating stack trace to be printed on the "git push" console. Fixed!

Enhancements:

• New pull-request control: require ALL reviewers to approve.
• New Jira policy option: control the branches that Jira policy applies to using a regex.

- - - - -

Since v2024.07.28, Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

Bitbucket 9.x Compatibility. Since v2024.07.28, Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ (Since the prices for these two apps are identical, this is essentially a 2-for-1 deal).

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

Control-Freak is now a paid app.

Note: Paid customers of PR-Booster do not need to pay for Control-Freak. If you have an existing paid PR-Booster license, please email support@bit-booster.com to receive a 100% discount coupon code for Control-Freak.

For those without a current active paid PR-Booster license, you can use the code below to receive a 50% discount if you purchase licenses for both Control-Freak and PR-Booster together: https://promo.atlassian.com/QIB4PQ (Since the prices for these two apps are identical, this is essentially a 2-for-1 deal).

Note: Control-Freak will remain free for all existing paid PR-Booster clients indefinitely.

Performance improvements, a bugfix, and improvement to Jira grandfathering logic:

• The "sortable columns" feature on the Project drilldown page is much faster now.
• The "sortable columns" feature introduced a bug where it would complain if it saw commits that had no valid author email address. Fixed! (Bug #547).
• Jira grandfathering logic vastly improved. Jira checks should NEVER fire anymore on commits that already sit behind "Jira-protected" branches.

Performance improvements, a bugfix, and improvement to Jira grandfathering logic:

• The "sortable columns" feature on the Project drilldown page is much faster now.
• The "sortable columns" feature introduced a bug where it would complain if it saw commits that had no valid author email address. Fixed! (Bug #547).
• Jira grandfathering logic vastly improved. Jira checks should NEVER fire anymore on commits that already sit behind "Jira-protected" branches.

Fixed "Permissions Audit" feature:

• The "sortable repos" feature broke the "permissions audit" feature. Oops. Fixed!
• Turned out "permissions audit" was limited to checking at most 2,000 repositories. That limit has also been fixed and it now works with unlimited repositories.

Version 2024.06.10 also includes a small cosmetic bug fix related to "sortable repos":

• sort-by-name used a slightly weird total ordering (e.g., the words "git", "qa", "beta", and "alpha" came before "apple"). Also fixed!

Fixed "Permissions Audit" feature:

• The "sortable repos" feature broke the "permissions audit" feature. Oops. Fixed!
• Turned out "permissions audit" was limited to checking at most 2,000 repositories. That limit has also been fixed and it now works with unlimited repositories.

Version 2024.06.10 also includes a small cosmetic bug fix related to "sortable repos":

• sort-by-name used a slightly weird total ordering (e.g., the words "git", "qa", "beta", and "alpha" came before "apple"). Also fixed!

First I want to re-iterate that as of "v2024.05.28" Control Freak now includes SORTABLE REPOS on the "Project" drilldown page! That feature took us literally months to implement - very challenging!

Now, back to the "v2024.06.01" release notes: We added a new config variation for new-branch creation for Pull-Request protected branch patterns. Suppose you mandate that all branches that match the pattern "release/*" must receive pull requests (no direct pushes allowed), whereas "master" can receive direct pushes. But then you want to start a brand new "release/v2024.06.x" branch from a 'master' commit. This causes a chicken-and-egg problem: that initial commit has never received a pull-request. Should Control Freak allow the new branch to be created?

Version v2024.06.01 resolves this conundrum by allowing a new Pull-Request variation:

[x] Allow [Repository Admins] to create new branches that temporarily break this rule (for the initial starting commits only).

First I want to re-iterate that as of "v2024.05.28" Control Freak now includes SORTABLE REPOS on the "Project" drilldown page! That feature took us literally months to implement - very challenging!

Now, back to the "v2024.06.01" release notes: We added a new config variation for new-branch creation for Pull-Request protected branch patterns. Suppose you mandate that all branches that match the pattern "release/*" must receive pull requests (no direct pushes allowed), whereas "master" can receive direct pushes. But then you want to start a brand new "release/v2024.06.x" branch from a 'master' commit. This causes a chicken-and-egg problem: that initial commit has never received a pull-request. Should Control Freak allow the new branch to be created?

Version v2024.06.01 resolves this conundrum by allowing a new Pull-Request variation:

[x] Allow [Repository Admins] to create new branches that temporarily break this rule (for the initial starting commits only).

We've added some columns to the "Repositories" page (size, activity, last commit time), and made them sortable.

We've also added a special "All Repositories" version of this same page that lists *ALL* repositories across an organization (not just the ones that belong under a single Project).

We've added some columns to the "Repositories" page (size, activity, last commit time), and made them sortable.

We've also added a special "All Repositories" version of this same page that lists *ALL* repositories across an organization (not just the ones that belong under a single Project).

Fixed bug:

• In a personal fork, the "[x] - enable for this personal fork" control was doing nothing (couldn't be enabled).

Added feature:

• New control: max commit message length.

Fixed bug:

• In a personal fork, the "[x] - enable for this personal fork" control was doing nothing (couldn't be enabled).

Added feature:

• New control: max commit message length.

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Jira policy can now be configured in three ways:

Jira Policy Applies To:

1.) All Commits

2.) Regular Commits Only (e.g., ignore merge commits)

3.) Merge Commits Only (e.g., ignore regular commits)

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Jira policy can now be configured in three ways:

Jira Policy Applies To:

1.) All Commits

2.) Regular Commits Only (e.g., ignore merge commits)

3.) Merge Commits Only (e.g., ignore regular commits)

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Some small improvements to the "User Permissions Audit" feature:

• Download as CSV works properly now (before it would ONLY download the permissions audit of the logged in user, regardless of what user had been queried). Fixed!
• Improved the CSV downloaded filename to include the current date (yyyy.mm.dd).
• Finally, the report (in both CSV and HTML formats) now inserts an extra blank row before each new Project row. Personally I find this makes it much easier to read the report!

Enjoy!

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Some small improvements to the "User Permissions Audit" feature:

• Download as CSV works properly now (before it would ONLY download the permissions audit of the logged in user, regardless of what user had been queried). Fixed!
• Improved the CSV downloaded filename to include the current date (yyyy.mm.dd).
• Finally, the report (in both CSV and HTML formats) now inserts an extra blank row before each new Project row. Personally I find this makes it much easier to read the report!

Enjoy!

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two small fixes:

• The "commit regex miss" help message was not correctly grouped in the right override grouping under the hood.
• Adjusted the hook to scan at most 333 commits instead of 999 commits (performance improvement).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two small fixes:

• The "commit regex miss" help message was not correctly grouped in the right override grouping under the hood.
• Adjusted the hook to scan at most 333 commits instead of 999 commits (performance improvement).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two small fixes:

• The "commit regex miss" help message was not correctly grouped in the right override grouping under the hood.
• Adjusted the hook to scan at most 333 commits instead of 999 commits (performance improvement).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two small fixes:

• The "commit regex miss" help message was not correctly grouped in the right override grouping under the hood.
• Adjusted the hook to scan at most 333 commits instead of 999 commits (performance improvement).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Improved rejection message wordings (e.g., replaced all instaces of "JIRA" with "Jira" - small things like that).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Improved rejection message wordings (e.g., replaced all instaces of "JIRA" with "Jira" - small things like that).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Improved rejection message wordings (e.g., replaced all instaces of "JIRA" with "Jira" - small things like that).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Small enhancement: Improved rejection message wordings (e.g., replaced all instaces of "JIRA" with "Jira" - small things like that).

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Fixed a bug:

• The case-insensitive tag check no longer blocks tag edits (e.g., via "git push --force --tags")

We also added more "Tag Policy" controls:

• Who can create tags? Admins or Regular Users
• Who can delete tags? Admins or Regular Users
• Who can edit tags? Admins or Regular Users or Disabled
• Allowed Tag Types? Annotated or Lightweight or Both
• Allow Non-Commit Tags? Yes or No

Note: Due to a bug in Bitbucket we can only enforce the lightweight vs. annotated tag rule during "git push" operations. Tags created directly in the Bitbucket web UI or via REST do not currently include any data that would allow us to distinguish annotated from lightweight during the pre-receive hook.

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Fixed a bug:

• The case-insensitive tag check no longer blocks tag edits (e.g., via "git push --force --tags")

We also added more "Tag Policy" controls:

• Who can create tags? Admins or Regular Users
• Who can delete tags? Admins or Regular Users
• Who can edit tags? Admins or Regular Users or Disabled
• Allowed Tag Types? Annotated or Lightweight or Both
• Allow Non-Commit Tags? Yes or No

Note: Due to a bug in Bitbucket we can only enforce the lightweight vs. annotated tag rule during "git push" operations. Tags created directly in the Bitbucket web UI or via REST do not currently include any data that would allow us to distinguish annotated from lightweight during the pre-receive hook.

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Fixed a bug:

• The case-insensitive tag check no longer blocks tag edits (e.g., via "git push --force --tags")

We also added more "Tag Policy" controls:

• Who can create tags? Admins or Regular Users
• Who can delete tags? Admins or Regular Users
• Who can edit tags? Admins or Regular Users or Disabled
• Allowed Tag Types? Annotated or Lightweight or Both
• Allow Non-Commit Tags? Yes or No

Note: Due to a bug in Bitbucket we can only enforce the lightweight vs. annotated tag rule during "git push" operations. Tags created directly in the Bitbucket web UI or via REST do not currently include any data that would allow us to distinguish annotated from lightweight during the pre-receive hook.

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Fixed a bug:

• The case-insensitive tag check no longer blocks tag edits (e.g., via "git push --force --tags")

We also added more "Tag Policy" controls:

• Who can create tags? Admins or Regular Users
• Who can delete tags? Admins or Regular Users
• Who can edit tags? Admins or Regular Users or Disabled
• Allowed Tag Types? Annotated or Lightweight or Both
• Allow Non-Commit Tags? Yes or No

Note: Due to a bug in Bitbucket we can only enforce the lightweight vs. annotated tag rule during "git push" operations. Tags created directly in the Bitbucket web UI or via REST do not currently include any data that would allow us to distinguish annotated from lightweight during the pre-receive hook.

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Introducing "Tag Policy" ! Here are the new controls around Tag Policy:

• Allow only admins to create tags
• Block new tags that differ only by case (e.g., "v1.2.3" vs. "V1.2.3")
• Require new tags to match a pre-defined regex rule

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Introducing "Tag Policy" ! Here are the new controls around Tag Policy:

• Allow only admins to create tags
• Block new tags that differ only by case (e.g., "v1.2.3" vs. "V1.2.3")
• Require new tags to match a pre-defined regex rule

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Introducing "Tag Policy" ! Here are the new controls around Tag Policy:

• Allow only admins to create tags
• Block new tags that differ only by case (e.g., "v1.2.3" vs. "V1.2.3")
• Require new tags to match a pre-defined regex rule

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Introducing "Tag Policy" ! Here are the new controls around Tag Policy:

• Allow only admins to create tags
• Block new tags that differ only by case (e.g., "v1.2.3" vs. "V1.2.3")
• Require new tags to match a pre-defined regex rule

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two new controls:

• New control: Allow only admins to create branches.
• New control: Block new branches that differ only by case (e.g., main vs. Main)

One bugfix:

• JQL queries that result in HTTP 401 (unauthenticated) now raise a proper error and invitation for user to refresh their (likely stale) oauth token.

One diagnostic improvement:

• All Jira JQL query replies that cause a git action to be blocked/rejected now include the user information by which Jira was queried. This should help users and companies better troubleshoot situations where the Jira integration is misconfigured.

(note: v2023.10.08 is identical to v2023.10.07 except that it was recompiled against Javac 1.8.x to ensure Java 8 compatibility).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two new controls:

• New control: Allow only admins to create branches.
• New control: Block new branches that differ only by case (e.g., main vs. Main)

One bugfix:

• JQL queries that result in HTTP 401 (unauthenticated) now raise a proper error and invitation for user to refresh their (likely stale) oauth token.

One diagnostic improvement:

• All Jira JQL query replies that cause a git action to be blocked/rejected now include the user information by which Jira was queried. This should help users and companies better troubleshoot situations where the Jira integration is misconfigured.

(note: v2023.10.08 is identical to v2023.10.07 except that it was recompiled against Javac 1.8.x to ensure Java 8 compatibility).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two new controls:

• New control: Allow only admins to create branches.
• New control: Block new branches that differ only by case (e.g., main vs. Main)

One bugfix:

• JQL queries that result in HTTP 401 (unauthenticated) now raise a proper error and invitation for user to refresh their (likely stale) oauth token.

One diagnostic improvement:

• All Jira JQL query replies that cause a git action to be blocked/rejected now include the user information by which Jira was queried. This should help users and companies better troubleshoot situations where the Jira integration is misconfigured.

(note: v2023.10.08 is identical to v2023.10.07 except that it was recompiled against Javac 1.8.x to ensure Java 8 compatibility).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

Two new controls:

• New control: Allow only admins to create branches.
• New control: Block new branches that differ only by case (e.g., main vs. Main)

One bugfix:

• JQL queries that result in HTTP 401 (unauthenticated) now raise a proper error and invitation for user to refresh their (likely stale) oauth token.

One diagnostic improvement:

• All Jira JQL query replies that cause a git action to be blocked/rejected now include the user information by which Jira was queried. This should help users and companies better troubleshoot situations where the Jira integration is misconfigured.

(note: v2023.10.08 is identical to v2023.10.07 except that it was recompiled against Javac 1.8.x to ensure Java 8 compatibility).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• Small preventive fix to guard against long "git log" invocations. Control-Freak will now analyse at most the top 999 commits across all pre-existing branches (no limit on # of pushed commits) when evaluating a pull-request or push for compliance.

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• Small preventive fix to guard against long "git log" invocations. Control-Freak will now analyse at most the top 999 commits across all pre-existing branches (no limit on # of pushed commits) when evaluating a pull-request or push for compliance.

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• The "rebase-and-merge" / "rebase-and-fast-forward" merge options are not respecting the "Ignore Clean Rebases" check under Jira Policy. Fixed ! Thanks to PW for reporting this (issue #267).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• The "rebase-and-merge" / "rebase-and-fast-forward" merge options are not respecting the "Ignore Clean Rebases" check under Jira Policy. Fixed ! Thanks to PW for reporting this (issue #267).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• The "rebase-and-merge" / "rebase-and-fast-forward" merge options are not respecting the "Ignore Clean Rebases" check under Jira Policy. Fixed ! Thanks to PW for reporting this (issue #267).

Full changelog below the fold.

---

If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Data Center. Revenue from PR-Booster helps fund Control Freak's maintenance.

---

One bugfix:

• The "rebase-and-merge" / "rebase-and-fast-forward" merge options are not respecting the "Ignore Clean Rebases" check under Jira Policy. Fixed ! Thanks to PW for reporting this (issue #267).