Skip to:

Marketplace

 Control Freak - Commit Checks and Jira Hooks for Bitbucket

works with Bitbucket Cloud, Bitbucket Server 7.0.0 - 8.19.18, Bitbucket Data Center 7.0.0 - 9.6.5 and more

OVERALL RATINGS

INSTALLS

815

SUPPORT

  • Partner Supported

Key highlights of the app"A must-have app!" Validates all pushes, merges, and web UI file edits to ensure they comply with your corporate Git policy

watch  Control Freak - Commit Checks and Jira Hooks for Bitbucket video

A pre-receive githook to ensure better commit msgs

- Enforce a rebase, squash, or git flow policy if you want!

- Avoid repositories with bad defaults ("main" can be deleted!)

- Run a Gerrit workflow ("Needs Work" PRs can't merge)

- Supports regex like YACC & ScriptRunner

Never see another missing Jira ticket ref / ID

- Define protected branches using Bitbucket's branching model

- Can check Jira issue status, assignee, or better yet, any arbitrary JQL

- Options: can ignore merge commits, submodule updates, clean rebases & cherry picks

Helpful block messages keep developers productive

- Rejection messages include specific steps to fix the problem

- Example: block large files and suggest LFS

- Empowers developers to fix their mistakes

- Simple architecture: no external webhook or post-receive triggers

Supporting media

More details

Control Freak is a collection of push and merge hooks to reject commits based on pre-configured rules. Available rules include:

  • Enforce JIRA linking for git commit messages (similar to YACC but better!)
  • Branch naming policy
  • Block large files
  • Block deletes / rewrites / force-pushes of important branches
  • Enforce a rebase or squash workflow
  • Block self-approvals on pull-requests
  • Author / committer name and email checks
  • Block empty commits
  • Block foxtrot merges

Configuration can be applied per-repo, per-project, or globally. Rules can be applied per repository type (regular vs. personal vs. fork). User and Group based exemption lists let service accounts, bots, and power users avoid the checks when necessary.

Our checking logic is optimized to run at most two "git rev-list" commands per push or merge, no matter how many rules you have enabled.

---

ABOUT BIT-BOOSTER

We also make:

Resources

Privacy and Security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Version information

Version 2025.08.29for Bitbucket Data Center 7.0.0 - 9.6.5

Release date
Aug 30th 2025
Summary
Yet another attempt at perfecting our Jira DC vs. Jira Cloud probing logic
Details

Version v2025.08.29 contains 1 important fix:

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

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

- - - - -

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

Payment model
Paid via Atlassian
License type
Commercial - no charge
Explore all Data Center versions

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow