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!

Three new features:

• Require minimum # of approvals to merge pull request.
• Block merge if "Needs Work" reviews are present.
• Skip Jira checks if commit message contains a special "Jira Skip" message (customizable).

The approval and disapproval logic is integrated with the branching model (like most of Control Freak's checks). The approval and disapproval logic can also be configured to only consider users with write access.

Important bugfix:

Pushing new branches sometimes caused Control Freak do run complete git repo traversals using "git log". This would happen when the "Apply JIRA Policy Against" choices were either disabled or only turned on for the "All Others" branch choice.

Fixed!

Important bugfix:

Pushing new branches sometimes caused Control Freak do run complete git repo traversals using "git log". This would happen when the "Apply JIRA Policy Against" choices were either disabled or only turned on for the "All Others" branch choice.

Fixed!

The branch names of branches created through the Bitbucket UI are now checked to see if they comply with Control Freak's branch naming policy. (Before this release only new branches created via push were checked).

A regression was introduced in previous Control Freak version 2018.07.19:

• Already vetted commits were re-triggering JIRA policy unnecessarily. For example sync-merges or even pushing against a new branch would cause the entire line to be re-examined against the JIRA policy.
• This breaks the fundamental contract of Control Freak: once a given commit has passed verification, it should never be re-verified, no matter what branch it might later appear on.
• Small bug fix: empty commits are properly grandfathered now (by applying the same fundamental contract to the "empty commits" check).

Fix for issue #5 - "Authorship Policy rejecting push"

We noticed two problems with the author-checking logic:

• Faulty behaviour if Bitbucket user database contained 2 or more users with the same email address.
• If current-logged-in-user matches along with other potential users, then current-logged-in-user should be preferred.

Both of these problems are fixed with version v.2018.07.26 of Control Freak.

Version v2017.07.19 of Control Freak released 16 hours ago is a significant release with several important new features, including:

• JIRA checking can ignore merge commits
• JIRA checking can ignore submodule updates
• Introduced new "JIRA Project Whitelist" (e.g., for when a given repository is only allowed to commit against a subset of a company's JIRA projects).

Unfortunately a few bugs managed to sneak out with that release. We believe we've fixed them all as of this release (v2017.07.21):

• The "ensure author = JIRA assignee" logic had an off-by-one error on the email check, causing all commits to always be rejected if this rule was enabled.
• The JIRA project whitelist only worked if the list contained a single entry.

The override groupings were too large in the previous version, making it harder to leverage the value of the higher-level project and global settings.

In particular, "Branch Naming Policy," "JIRA Project Whitelist," and "JIRA Ticket Checking Logic" are now each in their own separate groups, making it easier to tweak and override particular settings for a given repo or project.

Several enhancements introduced in this version:

• JIRA policy can now ignore merges
• JIRA policy can now ignore submodule updates
• Ability to restrict JIRA policy to only check tickets that match a predefined JIRA project whitelist.
• Ability to override ALL settings at "project" and "repository" levels. (Before just a subset of the settings could be overridden).

Also some cosmetic bugs around the override mechanism in the admin web UI were fixed.

Attempts to enable the hooks for PERSONAL-FORKS or PERSONAL-REPOS would always result in the box remaining unchecked.

Fixed! The hooks can now be enabled/disabled as you please for PERSONAL-FORKS and PERSONAL-REPOS.

Logic unchanged, except licensing logic turned off so that Control Freak is now a free add-on.

One bugfix:

• Enabling the "all-other-branches" choice on JIRA hook essentially disabled the JIRA hook. Oops!

Two enhancements:

• New push/merge control: force commit author to match JIRA assignee.
• New branches that would normally require PRs (because their name matches a PR-protected pattern) are now allowed. But the new branch's starting-point must be a commit that's reachable from an existing PR-protected branch tip.

Also wordings on push/merge rejection messages improved throughout.

One bug fix:

• Attempting to modify user/group based exemptions on the global screen caused all exemptions at global level to be cleared. Fixed.

Ouch. That was a nasty bug.

Completed the rename to "Control Freak for Bitbucket Server". (This app used to be called "Bit-Booster - Global JIRA Hook").

Improved logic and response messages for some of the hooks:

• Foxtrot merges created by auto-merge now permitted. The importance of letting these merges through outweighs the annoyance of the foxtrot merge.
• Authorship hook now tries harder to find a matching user in Bitbucket's user database. Note: it still rejects the commit, but provides a better error message if it finds a match.
• The Authorship hook now responds with a much improved error message, helping users fix this problem on their own.

• Repository and Project overrides are available now for more of the config (e.g., authorship policy and branch naming policy can now be overridden).
• Fixed bug that caused an exception in some situations when a branch delete was pushed.

Fixed bug in JIRA logic

• JIRA checker would blow up when analyzing a merge from a protected branch to another protected branch (from sending empty JQL query to JIRA).

Enhancement:

- Unanticipated errors (e.g. RuntimeException) are now caught and printed directly in the end-user's UI.

Bug fixes:

- Some cross-repo merge checks were failing with RuntimeException because git alternates were not set properly, and so git commands could no locate all the necessary git objects.

- Enforce "Branching Policy" rule was blocking new "master" branch creation when hook the was enabled for empty repos. Basically a chicken and egg problem. Fixed.