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.

---

• New Feature: "Configuration Locks - All Projects" Config Screen

This screen helps Bitbucket Admins quickly understand which projects have overridden Control-Freak's "Configuration Lock" property. It also helps Admins quickly apply "lock" or "unlock" overrides to several projects at once.

In essence this new feature is both a productivity enhancer for Bitbucket admins, as well as a useful "deviations" report with respect to this specific configuration option.

(Note: we plan to roll out similar screens for other important Control-Freak config options. But for now we're just starting out with this first experiment - an "All Projects At Once" screen for the "Configuration Lock" property).

Note: v2022.08.09 fixes a small 404 caused by a typo in an admin screen.

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.

---

• New Feature: "Configuration Locks - All Projects" Config Screen

This screen helps Bitbucket Admins quickly understand which projects have overridden Control-Freak's "Configuration Lock" property. It also helps Admins quickly apply "lock" or "unlock" overrides to several projects at once.

In essence this new feature is both a productivity enhancer for Bitbucket admins, as well as a useful "deviations" report with respect to this specific configuration option.

(Note: we plan to roll out similar screens for other important Control-Freak config options. But for now we're just starting out with this first experiment - an "All Projects At Once" screen for the "Configuration Lock" property).

Note: v2022.08.09 fixes a small 404 caused by a typo in an admin screen.

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

---

Backported all recent features/bugfixes back to our Bitbucket 5.x/6.x compatible series.

All features/bugfixes introduced since v2022.04.09 have been back-ported. See Control-Freak's marketplace.atlassian.com "version history" page for more information.

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

---

Backported all recent features/bugfixes back to our Bitbucket 5.x/6.x compatible series.

All features/bugfixes introduced since v2022.04.09 have been back-ported. See Control-Freak's marketplace.atlassian.com "version history" page for more information.

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.

---

• New Feature: "Configuration Locks - All Projects" Config Screen

This screen helps Bitbucket Admins quickly understand which projects have overridden Control-Freak's "Configuration Lock" property. It also helps Admins quickly apply "lock" or "unlock" overrides to several projects at once.

In essence this new feature is both a productivity enhancer for Bitbucket admins, as well as a useful "deviations" report with respect to this specific configuration option.

(Note: we plan to roll out similar screens for other important Control-Freak config options. But for now we're just starting out with this first experiment - an "All Projects At Once" screen for the "Configuration Lock" property).

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.

---

• New Feature: "Configuration Locks - All Projects" Config Screen

This screen helps Bitbucket Admins quickly understand which projects have overridden Control-Freak's "Configuration Lock" property. It also helps Admins quickly apply "lock" or "unlock" overrides to several projects at once.

In essence this new feature is both a productivity enhancer for Bitbucket admins, as well as a useful "deviations" report with respect to this specific configuration option.

(Note: we plan to roll out similar screens for other important Control-Freak config options. But for now we're just starting out with this first experiment - an "All Projects At Once" screen for the "Configuration Lock" property).

CONTROL FREAK IS 5 YEARS OLD !

It all started on August 4th, 2017, with our submission to Atlassian's Codegeist 2017 hackathon. We are proud to report that we received zero likes, zero comments, and the Atlassian judges (for the competition) did not mention us. :-) :-) :-) Here's our original submission:

https://devpost.com/software/bit-booster-global-jira-foxtrot-hook

To celebrate our 5th birthday, we have implemented two new features:

---

• Jira-Impersonation: The connection to Jira can be configured to use a specific Bitbucket account. This can be especially useful when using service-accounts / ssh-keys.
• Support for Project Links. You can now add "$PROJECT_LINKS" to the Jira Project Whitelist setting to only check the tickets that correspond to the current repository's project links!

p.s. 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!

CONTROL FREAK IS 5 YEARS OLD !

It all started on August 4th, 2017, with our submission to Atlassian's Codegeist 2017 hackathon. We are proud to report that we received zero likes, zero comments, and the Atlassian judges (for the competition) did not mention us. :-) :-) :-) Here's our original submission:

https://devpost.com/software/bit-booster-global-jira-foxtrot-hook

To celebrate our 5th birthday, we have implemented two new features:

---

• Jira-Impersonation: The connection to Jira can be configured to use a specific Bitbucket account. This can be especially useful when using service-accounts / ssh-keys.
• Support for Project Links. You can now add "$PROJECT_LINKS" to the Jira Project Whitelist setting to only check the tickets that correspond to the current repository's project links!

p.s. 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!

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.

---

Fixed issues: #247, #245, #232, #231

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.

---

Fixed issues: #247, #245, #232, #231

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 significant new feature implemented:

Issue #156 - How can i make a globally configured features not override-able at Project / Repo level (by Project / Repo admins).

Done ! Enjoy !

Any Project or Repository can now be designated as "LOCKED" in Control-Freak which means *only* Bitbucket Global Admins can adjust its config. When a Project or Repository is marked as "LOCKED" that means Project Admins and Repository Admins can no longer touch the Control-Freak config for that repository (or project).

Note: all Control-Freak config edits are always logged to the Bitbucket Audit Log, regardless.

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 significant new feature implemented:

Issue #156 - How can i make a globally configured features not override-able at Project / Repo level (by Project / Repo admins).

Done ! Enjoy !

Any Project or Repository can now be designated as "LOCKED" in Control-Freak which means *only* Bitbucket Global Admins can adjust its config. When a Project or Repository is marked as "LOCKED" that means Project Admins and Repository Admins can no longer touch the Control-Freak config for that repository (or project).

Note: all Control-Freak config edits are always logged to the Bitbucket Audit Log, regardless.

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.

---

A few changes:

• This release makes Control Freak fully compatible with Bitbucket 8.x.
• We updated our "pom.xml", "spring/plugin-context.xml", and "atlassian-plugin.xml" metadata files to bring them up to date with Atlassian's latest examples for Bitbucket plugins. We also did a dependency audit to make sure Control-Freak brings in zero additional dependencies (it only depends on libraries, if necessary, that are already present within Bitbucket Data Center).

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.

---

A few changes:

• This release makes Control Freak fully compatible with Bitbucket 8.x.
• We updated our "pom.xml", "spring/plugin-context.xml", and "atlassian-plugin.xml" metadata files to bring them up to date with Atlassian's latest examples for Bitbucket plugins. We also did a dependency audit to make sure Control-Freak brings in zero additional dependencies (it only depends on libraries, if necessary, that are already present within Bitbucket Data Center).

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 change:

• This release makes Control Freak compatible with Bitbucket 8.x.

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 change:

• This release makes Control Freak compatible with Bitbucket 8.x.

Note: PR-Booster is not yet 8.x compatible. We have made good progress implementing all the 8.x changes required for PR-Booster (it was quite significant) and we will release an 8.x compatible version of PR-Booster by June 24th, 2022.

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 change:

• This release makes Control Freak compatible with Bitbucket 8.x.

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 change:

• This release makes Control Freak compatible with Bitbucket 8.x.

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 enhancement in this release:

• Added additional control for branch creation: [x] - A valid Jira ticket based on Jira Policy (see below) When "new branch" naming policy mandates Jira references in the branch name, the "new branch" can now also be mandated to use the same logic as the regular Jira Policy (e.g., jira ticket assigned to current bitbucket user; disallow Done/Complete statuses, etc). Implements feature request #105.

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 enhancement in this release:

• Added additional control for branch creation: [x] - A valid Jira ticket based on Jira Policy (see below) When "new branch" naming policy mandates Jira references in the branch name, the "new branch" can now also be mandated to use the same logic as the regular Jira Policy (e.g., jira ticket assigned to current bitbucket user; disallow Done/Complete statuses, etc). Implements feature request #105.

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 fix in this release:

• Successfully re-certified for DC (Data Center) compatibility.

Also worth noting that our previous "Server-Only" release included a fix for bug #215 (editing user/group exemptions via REST), and so this is the first DC compatible release to also contain that fix.

Please note:

• DC certification requires a lot of work and expense on our part. We load-tested Control Freak on production-level hardware with 1-node, 2-node, and 4-node Bitbucket clusters, each with 50,000+ repositories. This is considerable expense for us - and is why there are few fewer free Atlassian plugins these days! Please consider purchasing a PR-Booster license. Developers love PR-Booster, and its "Amend" and "Squash" buttons work very nicely together with Control-Freak!

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 fix in this release:

• Successfully re-certified for DC (Data Center) compatibility.

Also worth noting that our previous "Server-Only" release included a fix for bug #215 (editing user/group exemptions via REST), and so this is the first DC compatible release to also contain that fix.

Please note:

• DC certification requires a lot of work and expense on our part. We load-tested Control Freak on production-level hardware with 1-node, 2-node, and 4-node Bitbucket clusters, each with 50,000+ repositories. This is considerable expense for us - and is why there are few fewer free Atlassian plugins these days! Please consider purchasing a PR-Booster license. Developers love PR-Booster, and its "Amend" and "Squash" buttons work very nicely together with Control-Freak!

One fix:

• Our fix in previous version for #215 - "cannot set exempt groups/users via REST" - introduce a regression such that doing a REST POST to set Control Freak settings would throw a NullPointerException is no exempt users or exempt groups were specified in the JSON Post payload. Fixed !

-----

Note: if you are running Control Freak on a DC instance, the plugin manager will not see this release (we are currently recertifying for DC). You can force the plugin manager to take this upgrade by clicking on "Manage Apps" --> "Upload App" and then providing this URL:

https://marketplace.atlassian.com/download/apps/1217635/version/202203095

One fix, one feature removal:

• Fix issue #215 - cannot set exempt groups/users via REST
• Removed MergeBase vulnerability scanning. Please try out MergeBase using their dedicated CodeGreen App instead!

-----

Note: if you are running Control Freak on a DC instance, the plugin manager will not see this release (we are currently recertifying for DC). You can force the plugin manager to take this upgrade by clicking on "Manage Apps" --> "Upload App" and then providing this URL: https://marketplace.atlassian.com/download/apps/1217635/version/202202075

Full changelog below the fold.

---

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

---

Added diagnostic/tracing page to Control-Freak to help troubleshoot performance issues in Control-Freak.

To try this page: <repository> --> <settings> --> <control freak> --> "logging/tracing" link.

Tracing must be enabled per repository before tracing data is collected. The page still contains useful information even if no tracing data has been collected (e.g., git version, java version, control-freak version, repository size, number of commits, free memory, etc).

Full changelog below the fold.

---

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

---

Added diagnostic/tracing page to Control-Freak to help troubleshoot performance issues in Control-Freak.

To try this page: <repository> --> <settings> --> <control freak> --> "logging/tracing" link.

Tracing must be enabled per repository before tracing data is collected. The page still contains useful information even if no tracing data has been collected (e.g., git version, java version, control-freak version, repository size, number of commits, free memory, etc).

Fixed 1 bug:

• Control-Freak's REST api for getting/setting config was not behaving correctly with "tagDeletesAllowed" and "tagCreatesAllowed" keys. Issue #207.

Implemented 1 enhancement:

• Author/Committer meta-data can now be configured to validate only the email-address instead of the user's full "email + name" metadata. Issue #208.

Note: The "Full Security Report" that reports on known-vulnerabilities in dependencies (provided by MergeBase) is no longer a free feature, and requires a valid MergeBase CodeGreen plugin installation. The "Summary Report" remains free.

Fixed 1 bug:

• Control-Freak's REST api for getting/setting config was not behaving correctly with "tagDeletesAllowed" and "tagCreatesAllowed" keys. Issue #207.

Implemented 1 enhancement:

• Author/Committer meta-data can now be configured to validate only the email-address instead of the user's full "email + name" metadata. Issue #208.

Note: The "Full Security Report" that reports on known-vulnerabilities in dependencies (provided by MergeBase) is no longer a free feature, and requires a valid MergeBase CodeGreen plugin installation. The "Summary Report" remains free.

Full changelog below the fold.

---

Please check out our other startup! We are working on software supply chain security at mergebase.com. Send us an email at julius@mergebase.com !

---

• Fixed issue #198 - Pushing git tags throws error in control freak
• Fixed issue #199 - Control Freak plugin - Null pointer exception: displayId
• Fixed some issues with the embedded MergeBase vulnerable library scanner (e.g., fixing vulnerabilities wouldn't actually result in a final clear report - the older report would get stuck in the cache).

Full changelog below the fold.

---

Please check out our other startup! We are working on software supply chain security at mergebase.com. Send us an email at julius@mergebase.com !

---

• Fixed issue #198 - Pushing git tags throws error in control freak
• Fixed issue #199 - Control Freak plugin - Null pointer exception: displayId
• Fixed some issues with the embedded MergeBase vulnerable library scanner (e.g., fixing vulnerabilities wouldn't actually result in a final clear report - the older report would get stuck in the cache).

Full changelog below the fold.

---

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

---

• Control-Freak includes free known-vulnerability scans (provided by MergeBase CodeGreen). Because of significant improvements to this scanner we are resetting the config settings on this ("Disabled" and "Admins Only" are being reset to "Enabled"). I realise this will annoy some users. I'm sorry for that! Control-Freak is free, so please forgive me! Our engineer is a co-founder at MergeBase and this helped convince him to do all the Control-Freak fixes he provided recently!
• New feature: admins can provide a custom "banner message" that is printed whenever a push or a merge is rejected.
• Security bugfix: bump plexus-utils to 3.3.0 to eliminate some known-vulnerabilities
• CodeGreen scanner now supports .NET and Java transitives (without requiring any network calls!)

Full changelog below the fold.

---

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

---

• Control-Freak includes free known-vulnerability scans (provided by MergeBase CodeGreen). Because of significant improvements to this scanner we are resetting the config settings on this ("Disabled" and "Admins Only" are being reset to "Enabled"). I realise this will annoy some users. I'm sorry for that! Control-Freak is free, so please forgive me! Our engineer is a co-founder at MergeBase and this helped convince him to do all the Control-Freak fixes he provided recently!
• New feature: admins can provide a custom "banner message" that is printed whenever a push or a merge is rejected.
• Security bugfix: bump plexus-utils to 3.3.0 to eliminate some known-vulnerabilities
• CodeGreen scanner now supports .NET and Java transitives (without requiring any network calls!)

Full changelog below the fold.

---

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

---

Bugfix:

• Large file blocking would get confused if the path contained white spaces. Fixed.

Enhancements:

• Foxtrot blocking split into push/pull intercept. Default now is to only intercept foxtrots arriving via pushes. Intercepting foxtrots on pull requests only makes sense in organisations that use --ff and --ff-only merges, which is rare.
• Large file blocking error message more helpful for users trying to switch to LFS.
• Commit message regex failures can now include a custom error message.
• A REST endpoint for updating Control Freak settings is now available!

Full changelog below the fold.

---

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

---

Bugfix:

• Large file blocking would get confused if the path contained white spaces. Fixed.

Enhancements:

• Foxtrot blocking split into push/pull intercept. Default now is to only intercept foxtrots arriving via pushes. Intercepting foxtrots on pull requests only makes sense in organisations that use --ff and --ff-only merges, which is rare.
• Large file blocking error message more helpful for users trying to switch to LFS.
• Commit message regex failures can now include a custom error message.
• A REST endpoint for updating Control Freak settings is now available!

Full changelog below the fold.

---

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

---

Three enhancements:

• "Tags" are now an option for Jira-Policy validation. If a tag is pushed that corresponds to an unprotected branch (or no branch at all!), Jira-Policy validation can now be enabled to check the pushed tag.
• MergeBase CodeGreen security scans now consider transitive dependencies.
• Branch naming policy includes a new "hotfix" exemption (as well as the original "release" exemption) when requiring new branches match Jira tickets.

Two bug fixes:

• Fixed regression: submodule exemption for Jira-Policy stopped working a while back!
• Git-LFS pointer files are typically around 120-150 bytes. Don't block THEM if the max-file-size happens to be set lower than 150 bytes!

Full changelog below the fold.

---

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

---

Three enhancements:

• "Tags" are now an option for Jira-Policy validation. If a tag is pushed that corresponds to an unprotected branch (or no branch at all!), Jira-Policy validation can now be enabled to check the pushed tag.
• MergeBase CodeGreen security scans now consider transitive dependencies.
• Branch naming policy includes a new "hotfix" exemption (as well as the original "release" exemption) when requiring new branches match Jira tickets.

Two bug fixes:

• Fixed regression: submodule exemption for Jira-Policy stopped working a while back!
• Git-LFS pointer files are typically around 120-150 bytes. Don't block THEM if the max-file-size happens to be set lower than 150 bytes!

Full changelog below the fold.

---

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

---

Several important bug fixes:

• All Jira application-links are checked for Jira tickets now! Not just the primary! Note: our logic learns which Jira projects correspond to which Jira instances to keep network traffic to a minimum.
• Ability to specify "always-allowed" branch names.
• Moved Jira tickets are now handled properly. All earlier versions of Control-Freak caused a big headache when Jira tickets were moved (e.g., moving a ticket from TKT-123 to PROJ-345).
• Jira assignee validation ignoring ticket moves (fixed in v2020.09.22)

This release also contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Please see our documentation for more information about the new rebase/cherry-pick awareness.

Full changelog below the fold.

---

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

---

Several important bug fixes:

• All Jira application-links are checked for Jira tickets now! Not just the primary! Note: our logic learns which Jira projects correspond to which Jira instances to keep network traffic to a minimum.
• Ability to specify "always-allowed" branch names.
• Moved Jira tickets are now handled properly. All earlier versions of Control-Freak caused a big headache when Jira tickets were moved (e.g., moving a ticket from TKT-123 to PROJ-345).
• Jira assignee validation ignoring ticket moves (fixed in v2020.09.22)

This release also contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Please see our documentation for more information about the new rebase/cherry-pick awareness.

Full changelog below the fold.

---

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

---

Several important bug fixes, and support for multiple Jira application links:

• All Jira application-links are checked for Jira tickets now! Not just the primary! Note: our logic learns which Jira projects correspond to which Jira instances to keep network traffic to a minimum.
• Ability to specify "always-allowed" branch names.
• Moved Jira tickets are now handled properly. All earlier versions of Control-Freak caused a big headache when Jira tickets were moved (e.g., tickets that get moved for example from TKT-123 to PROJ-345).

This release also contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Please see v2020.09.14 release notes for more information about the new rebase/cherry-pick awareness.

Full changelog below the fold.

---

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

---

Several important bug fixes, and support for multiple Jira application links:

• All Jira application-links are checked for Jira tickets now! Not just the primary! Note: our logic learns which Jira projects correspond to which Jira instances to keep network traffic to a minimum.
• Ability to specify "always-allowed" branch names.
• Moved Jira tickets are now handled properly. All earlier versions of Control-Freak caused a big headache when Jira tickets were moved (e.g., tickets that get moved for example from TKT-123 to PROJ-345).

This release also contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Please see v2020.09.14 release notes for more information about the new rebase/cherry-pick awareness.

Full changelog below the fold.

---

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

---

This release contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Here's what the control looks like in the admin pages:

[x] Ignore clean rebases and cherry-picks of previously verified commits (defaults to "enabled").

This new feature makes rebase & cherry-pick workflows less annoying and more productive when combined with strict Jira checking. Subsequent Jira validations are skipped as long as the rebase and cherry-picks are clean (e.g., the underlying commit is unchanged). Full Jira validation happens the *very first* time the commit is pushed; subsequent rebases or cherry-picks can proceed even if Jira status or assignee changes.

Misc changes:

• MergeBase CodeGreen free security scans improved.

Full changelog below the fold.

---

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

---

This release contains one FANTASTIC new feature :-) :-) :-)

• Jira-validation can now be configured to be rebase/cherry-pick aware.

Here's what the feature looks like in the admin pages:

[x] Ignore clean rebases and cherry-picks of previously verified commits (defaults to "enabled").

This new feature makes rebase & cherry-pick workflows less annoying and more productive when combined with strict Jira checking. Subsequent Jira validations are skipped as long as the rebase and cherry-picks are clean (e.g., the underlying commit is unchanged). Full Jira validation happens the *very first* time the commit is pushed; subsequent rebases or cherry-picks can proceed even if Jira status or assignee changes.

Misc changes:

• MergeBase CodeGreen free security scans improved.

Full changelog below the fold.

---

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

---

One new enhancement:

• Control-Freak rules can now be ignored when pushes come from access keys (a.k.a.service accounts).

In future versions of Control Freak we may consider tying the exemption to specific access keys, but for now it's an all-or-nothing style control (e.g., allow all service accounts to skip the rules, or force all service accounts to follow the rules). This exemption can be set at the global, project, or repository level. It defaults to requiring service accounts to follow all rules (the current behavior).

Full changelog below the fold.

---

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

---

One new enhancement:

• Control-Freak rules can now be ignored when pushes come from access keys (a.k.a.service accounts).

In future versions of Control Freak we may consider tying the exemption to specific access keys, but for now it's an all-or-nothing style control (e.g., allow all service accounts to skip the rules, or force all service accounts to follow the rules). This exemption can be set at the global, project, or repository level. It defaults to requiring service accounts to follow all rules (the current behavior).

Full changelog below the fold.

---

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

---

Three bugfixes:

• The logic for disallowing self-approvals was not 100% correct at calculating which commits belonged to a PR and which belonged to the target branch. This bug would cause some approvals to get rejected as self-approvals when in fact they were proper approvals. Fixed!
• Editing the repo-level settings could sometimes fail with a "401-Only-Bitbucket-Admins-Can-Do-This" error. Fixed!
• The setting to disable the free MergeBase cyber security scans was only disabling scans associated with pushes. Scans available directly in the Web UI remained available even if the config was set to disable these. Fixed!

One enhancement:

• The MergeBase cyber security scans can now be enabled for admins-only. 3 settings: enabled, enabled-for-admins-only, and disabled.

Full changelog below the fold.

---

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

---

Three bugfixes:

• The logic for disallowing self-approvals was not 100% correct at calculating which commits belonged to a PR and which belonged to the target branch. This bug would cause some approvals to get rejected as self-approvals when in fact they were proper approvals. Fixed!
• Editing the repo-level settings could sometimes fail with a "401-Only-Bitbucket-Admins-Can-Do-This" error. Fixed!
• The setting to disable the free MergeBase cyber security scans was only disabling scans associated with pushes. Scans available directly in the Web UI remained available even if the config was set to disable these. Fixed!

One enhancement:

• The MergeBase cyber security scans can now be enabled for admins-only. 3 settings: enabled, enabled-for-admins-only, and disabled.

Full changelog below the fold.

---

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

---

One bugfix:

• Issue #134 - Some pushes result in "java.lang.ArrayIndexOutOfBoundsException: null." That should be fixed now.

One enhancement:

• We now provide cyber-security known-vulnerability scans directly in the Bitbucket Web UI, making them easier to understand and access for a broader range of users. In previous versions of Control Freak these scans printed results after successful "git push" operations, but not everyone uses "git push" or pays attention to success messages there.
• Note: the technology behind these vulnerability scans was provided through our collaboration with MergeBase Software Inc. (https://mergebase.com/).

Full changelog below the fold.

---

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

---

One bugfix:

• Issue #134 - Some pushes result in "java.lang.ArrayIndexOutOfBoundsException: null." That should be fixed now.

One enhancement:

• We now provide cyber-security known-vulnerability scans directly in the Bitbucket Web UI, making them easier to understand and access for a broader range of users. In previous versions of Control Freak these scans printed results after successful "git push" operations, but not everyone uses "git push" or pays attention to success messages there.
• Note: the technology behind these vulnerability scans was provided through our collaboration with MergeBase Software Inc. (https://mergebase.com/).

Full changelog below the fold.

---

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

---

Two new features:

• Cyber security known-vulnerability scans! Announcing our cyber security collaboration with the MergeBase Code Green scanner. More info here: https://bit-booster.com/control-freak-mergebase-code-green/
• Audit Logging! We implemented integration with Bitbucket's built-in audit log. All config changes to Control Freak are now logged to the audit log, helping admins and auditors understand when (and which users) have made changes to Control Freak settings.

One bug fix:

• Fixed a bug preventing Control Freak from being used with access key (e.g., ssh keys).

(Note: we have further improved the audit logging since the v2020.01.29 release last week).

Full changelog below the fold.

---

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

---

Two new features:

• Cyber security known-vulnerability scans! Announcing our cyber security collaboration with the MergeBase Code Green scanner. More info here: https://bit-booster.com/control-freak-mergebase-code-green/
• Audit Logging! We implemented integration with Bitbucket's built-in audit log. All config changes to Control Freak are now logged to the audit log, helping admins and auditors understand when (and which users) have made changes to Control Freak settings.

One bug fix:

• Fixed a bug preventing Control Freak from being used with access key (e.g., ssh keys).

(Note: we have further improved the audit logging since the v2020.01.29 release last week).

Full changelog below the fold.

---

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

---

One URGENT bugfix:

• Issue #99 - Saving config at the REPO or PROJECT level causes a 500 Internal Server Error. Regression caused by v2019.10.12.

One regular bugfix:

• Issue #96 - Some PRs / pushes blow up with "Control Freak: null at com.bitbooster.hook.C.buildResult(C.java:184)". Caused by a hard-to-trigger bug in Control Freak's commit parser.

One feature enhancement:

• Large file blocking now includes ability to set a lower size threshold for specific file types. For example, admins can define a general max file size of 50MB (for all files) alongside a lower limit of 300 bytes for *.pdf and *.zip. In this example *.pdf and *.zip files are forced to use Git LFS, even for small zip and pdf files.

Finally, error messaging also improved, especially around exceptions.

Full changelog below the fold.

---

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

---

One URGENT bugfix:

• Issue #99 - Saving config at the REPO or PROJECT level causes a 500 Internal Server Error. Regression caused by v2019.10.12.

One regular bugfix:

• Issue #96 - Some PRs / pushes blow up with "Control Freak: null at com.bitbooster.hook.C.buildResult(C.java:184)". Caused by a hard-to-trigger bug in Control Freak's commit parser.

One feature enhancement:

• Large file blocking now includes ability to set a lower size threshold for specific file types. For example, admins can define a general max file size of 50MB (for all files) alongside a lower limit of 300 bytes for *.pdf and *.zip. In this example *.pdf and *.zip files are forced to use Git LFS, even for small zip and pdf files.

Finally, error messaging also improved, especially around exceptions.

Full changelog below the fold.

---

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

---

1 new feature:

• Added new "Block large files" control. This helps prevent large binary files from getting accidentally added to the repository (often a permanent mistake!). The push rejection message can be configured to encourage use of "Git LFS" instead of regular git.

2 fixes:

• Branch deletes via Bitbucket Web UI are now blocked if Control Freak is setup to prevent the branch from being deleted. (Note: we are unable to block deletes triggered by the "Delete source branch after merging" control on the pull-request dialog).
• Pushes against empty repositories were causing RuntimeExceptions. Fixed! :-)

We also improved our error messages to help make triage and troubleshooting faster whenever Control Freak encounters unexpected internal errors.

Full changelog below the fold.

---

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

---

1 new feature:

• Added new "Block large files" control. This helps prevent large binary files from getting accidentally added to the repository (often a permanent mistake!). The push rejection message can be configured to encourage use of "Git LFS" instead of regular git.

2 fixes:

• Branch deletes via Bitbucket Web UI are now blocked if Control Freak is setup to prevent the branch from being deleted. (Note: we are unable to block deletes triggered by the "Delete source branch after merging" control on the pull-request dialog).
• Pushes against empty repositories were causing RuntimeExceptions. Fixed! :-)

We also improved our error messages to help make triage and troubleshooting faster whenever Control Freak encounters unexpected internal errors.

Based on feedback from DCHELP-938:

• No longer using the Atlassian internal user / group picker.
• No longer calling BranchType.getPrefix() via reflection to categorize pushes by branch type. Instead we're calling BranchModel.getClassifier().getType(MinimalRef).

Full changelog below the fold.

---

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

---

4 fixes:

• URGENT FIX: pushes/forks fail if author / committer metadata check enabled on Bitbucket 6.5+ with error: "InvalidRefNameException: --not is not a valid commit identifier" (#91).
• Branch Naming Policy now applies to branch creation via REST or Bitbucket UI.
• Branching model calculations no longer use reflection.
• "Except Release Branches" rule works again (v2019.08.26 regression).

1 new feature:

• Ignore Self-Approvals

When enabled, this changes how Control Freak counts approvals required to merge a PR. Authors and committers associated with the commits-in-play for the PR no longer have their "Approving" votes on the PR count towards the minimum vote threshold. Works best if the "[x] Committer must be a valid Bitbucket User" control has been checked for a few weeks beforehand.

Urgent bugfix: Control-Freak prevents PRs that span forks from merging on Bitbucket 6.0.0 or newer because of a java.lang.NoSuchMethodError: com.atlassian.bitbucket.scm.git.command.GitScmCommandBuilder.alternates(Ljava/lang/Iterable;)

Underlying cause: some core Bitbucket APIs went through some cleanup in 6.0.0 that unfortunately breaks Java bytecode reverse-compatibility (e.g., interface methods that were previously redundantly declared in both child and parent interfaces were removed from the child).

Thanks to Dennis Schumann for the bug report.

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

Fixed severe regression in v2019.03.27 that prevented all pushes from non-admin users when Control Freak was enabled.

Since we have removed "v2019.03.27" from our marketplace listing, here's the release notes from that version:

• Fix for Issue #76: let developer push new "development" or "production" branches if the branch-model permits those. (Previously only the wildcard patterns would be permitted).

Some other small improvements:

• Cleaned up wording on reject message when Control-Freak rejects direct file edits.
• We were able to adjust the current version's compatibility setting back to Bitbucket 5.8.0 thanks to some thorough testing. This should help companies making the transition to Bitbucket 6.x, since you can now upgrade Control-Freak as a single independent app upgrade beforehand.

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

Fix for Issue #70: Unable to merge PR. (Bug introduced in version 2019.02.18).

This version now works on Bitbucket 6.x.

If you find our free Control Freak app useful, please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server.

PR-Booster enhances your git workflow. Rebase, squash, amend, revert, and cherry-pick directly from Bitbucket. Ensure quality with automatic approvals retraction and needs-work retention. Save time with build status propagation. Revenue from PR-Booster helps fund maintenance for Control Freak, as well as our other free apps.

Issue #52 - JQL queries with quotes (or other disallowed JSON characters) were causing a java.lang.RuntimeException: Bad JIRA HTTP POST=400.

Fixed!