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

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:

• Pull-Request screen was spitting out an "IllegalArgumentException" error if "require # approvals" control was in force. Fixed!

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:

• Pull-Request screen was spitting out an "IllegalArgumentException" error if "require # approvals" control was in force. Fixed!

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:

• Pull-Request screen was spitting out an "IllegalArgumentException" error if "require # approvals" control was in force. Fixed!

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:

• Pull-Request screen was spitting out an "IllegalArgumentException" error if "require # approvals" control was in force. Fixed!

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:

• We noticed that 3rd party Bitbucket plugins and apps can be coded in ways to push git changes that evade Control-Freak rules. Fixed!

We also made improvements to our "User Permissions Audit Tool" feature (v2022.12.01):

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• We noticed that 3rd party Bitbucket plugins and apps can be coded in ways to push git changes that evade Control-Freak rules. Fixed!

We also made improvements to our "User Permissions Audit Tool" feature (v2022.12.01):

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• We noticed that 3rd party Bitbucket plugins and apps can be coded in ways to push git changes that evade Control-Freak rules. Fixed!

We also made improvements to our "User Permissions Audit Tool" feature (v2022.12.01):

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• We noticed that 3rd party Bitbucket plugins and apps can be coded in ways to push git changes that evade Control-Freak rules. Fixed!

We also made improvements to our "User Permissions Audit Tool" feature (v2022.12.01):

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• Direct edits (in Bitbucket Web UI) were skipping the "[x] - Always Require Pull Requests" control. Note: this was the only control they were skipping - direct edits still triggered all of the other controls.

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• Direct edits (in Bitbucket Web UI) were skipping the "[x] - Always Require Pull Requests" control. Note: this was the only control they were skipping - direct edits still triggered all of the other controls.

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• Direct edits (in Bitbucket Web UI) were skipping the "[x] - Always Require Pull Requests" control. Note: this was the only control they were skipping - direct edits still triggered all of the other controls.

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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:

• Direct edits (in Bitbucket Web UI) were skipping the "[x] - Always Require Pull Requests" control. Note: this was the only control they were skipping - direct edits still triggered all of the other controls.

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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.

---

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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.

---

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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.

---

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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.

---

Improvements to our new feature:

• The "User Permissions Audit Tool" helps admins review which Projects and Repositories users have access to. This version further improved this tool to include repository and project descriptions, and to allow downloading the audit results in CSV format.

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

• Control-Freak now includes a User Permissions Audit Tool to help admins review which Projects and Repositories users have access to.

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

• Control-Freak now includes a User Permissions Audit Tool to help admins review which Projects and Repositories users have access to.

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.

---

Two small enhancements:

• Jira regex adjusted to allow underscores in Jira project keys (e.g., "ABC_XYZ999-12345" now considered a valid Jira ticket).
• Specified <startup>late</startup> in the plugin metadata (this should resolve rare situations where the app fails to start).

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.

---

Two small enhancements:

• Jira regex adjusted to allow underscores in Jira project keys (e.g., "ABC_XYZ999-12345" now considered a valid Jira ticket).
• Specified <startup>late</startup> in the plugin metadata (this should resolve rare situations where the app fails to start).

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.

---

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.

---

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

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.

---

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.

---

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.

---

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.