Better Commit Policy for Bitbucket Data Center

Verify the changes (branches, tags, commits) and pull requests in Bitbucket against configurable rules
This app was previously called "Commit Policy Plugin for Bitbucket". It is still the same app you love, but it was renamed in Jan 2019.
How does it work?

Better Commit Policy checks the changes committed to your Bitbucket against a set of configurable rules, the commit policy.

When the rules are not satisfied, the commit is rejected. Rejected changes should be "fixed" to comply with the rules, and then be re-committed.

How is it different from Better Commit Policy for Jira?

It's simple: this app works by integrating the Better Commit Policy for Jira app with Bitbucket.

While the Jira app is Version Control System independent (supports Git, Subversion, Mercurial among others), this app provides native Bitbucket experience utilizing pull requests, web based editing, application links and more.

Why should I use commit policies?

As a result of enforcing rules on the changes submitted to and on the pull requests merged in Bitbucket, the quality of your processes, the traceability of your changes and the consistency of your source code dramatically improve.

Learn more by watching the intro video in the left.

Verify the commits and work securely

The rules can verify every aspect of the changes: the commit message, the changed files, the committer, the affected branches and tags.

Each rule:

  • can be limited to specific branches or directories
  • can combine multiple conditions with AND/OR
  • can show custom instructions to the developer when his/her commit is rejected
Verify the pull requests, too

In addition to pushing commits, merging pull requests are the other way to apply changes to the Bitbucket managed code.

Better Commit Policy verifies pull requests just as rigorously as pushes. Merging is enabled only if all commits in the pull request satisfy the policy.

Verify the changes made via the Bitbucket web interface

With Bitbucket you can make changes to the repository right in your browser:

  1. Bitbucket supports creating branches and tags.
  2. Power Editor (a Bitbucket app) even allows creating commits via the web UI!

All these changes are fully verified by Better Commit Policy. The integrity of your code is preserved, no matter where the changes are originated from.

Ready for the Enterprise

Unlike free alternatives, Better Commit Policy is:

No extra efforts

Better Commit Policy is the only commit checker app for Bitbucket that verifies commits before those are created! With "broken" commits effectively prevented, no efforts are wasted to fix those. Find out why →

Quick adoption

Let's face it: developers hate (and refuse) heavy-weight processes. Albeit being light-weight, Better Commit Policy prevents chaos and encourages good practices that everyone agrees upon. And it does so without losing agility.

Works with your current tools

Your team members can use any standard-compliant Git client (command-line, GUI tools, IDE integrations) on any Operating System.

Zero learning curve

After a couple of rejections, clean and precise commits become the new normal.

Verify the tags in your repositories
Verify the branches your developers create
  • Branch name must match a pattern
    • branch names must be one of the types "feature/*", "release/*" or "maintenance/*"
    • bugfix branch names must contain a test execution ID like "bugfix/1741"
  • Branch name must contain issue keys from a JQL query
    • story branch names must include a "Story" type issue from the currently running Scrum sprint like "story/CAL-123-shared-calendars"
    • bugfix branch names must include an unresolved "Bug" type issue assigned to the committer
Enforce useful commit messages
  • Commit message must contain issue keys from a JQL query
    • no changes accepted without at least one Jira issue associated
    • changes must refer to exactly one user story in the current sprint
    • changes must refer to unresolved bugs and change requests planned for the next maintenance version of project FOOBAR
  • Commit message must match a pattern
    • commit messages must be at least 10 characters long (excluding whitespace)
    • commit messages must start with a Jira issue key
Control the file additions / deletions / modifications
Who is who and who can do what?

Rigorous change control

Establish processes for compliance with ISO standards, IEC standards and industry regulations in:

  • defence
  • financial
  • avionics (success story)
  • automotive
  • medical
  • pharmaceutical
  • other safety-critical systems

Or, just make sure that every change to your code is introduced in a controlled and documented way!

End-to-end traceability

Accelerate requirements validation, compliance verification, impact analysis, coverage analysis and source code audits by bi-directionally linking Jira issues and source code changes:

  • requirements ⇔ code changes
  • epics ⇔ user stories ⇔ code changes
  • tasks / bugfixes ⇔ code changes
  • tests ⇔ code changes
  • change requests ⇔ sub-tasks ⇔ code changes
  • releases ⇔ issues ⇔ code changes

Faster code reviews & audits

Maintain development workflows for consistent repository, code & history.

By making small improvements (useful tips) in the way your team works, common questions like these will be automatically answered:

  • "Why was this changed?"
  • "Was it tested? In what environments?"
  • "Is this within the scope of the current release?"
  • "Who approved this merge?"
  • "Is there a programmatic test for this story?"

Who's using it?


How does it help me work better?


Better Commit Policy success story (Aviation)
Helping the developer team comply with regulations and software requirements

"In the aviation industry, we need to be able to prove to authorities how exactly each aerospace system requirement is fulfilled and by what part of the source code. Better Commit Policy makes it easy to manage our Jira work items towards those requirements, proactively control what is committed to our source code repositories, and ultimately, to comply with regulations."

– Kalen Brown, Associate Electrical and Computer Engineer

Read the story →
Better Commit Policy success story (Medical)
How developers of safety-critical systems at Philips manage source code changes

"Before using commit policies, our developers’ behavior was like in the wild west. We couldn’t match source code changes with Jira issues, it was almost impossible to understand what work has really been done, we wasted time. The Better Commit Policy app helps us maintain a manageable development process by enforcing some configurable rules in a friendly, but strict way."

– Yakov Yukhnovetsky, DevOps Engineer

Read the story →
Do you have an inspiring story
with the Better Commit Policy app?


We'd love to know!

For compliance reasons, we must ensure that every commit is associated with a valid Jira issue. This app allows us to satisfy that requirement. The support from Midori so far has been fantastic. I reported an issue and was promptly contacted by a senior developer who was able to identify the root cause of the problem and quickly provide a patch that resolved it.

Andrew F., Intronis

This app is a must-have to keep our repository clean. Its usage is as easy and intuitive as possible.

Eric F., CTA International

This app is a key tool in our DevOps process.

Subramanian O., Essilor

This app "just works". When I needed help, the support was really fast and good.

Valentin E., Open Technologies
more reviews →

Get the app free

  1. Install the app. (how to install?)
  2. Use the app completely free of charge. (note: its dependencies are paid apps)
  3. Ask questions or report problems any time by clicking the "Help" tab in the right bottom. (how to get support?)
  4. Get the latest Better Commit Policy for Bitbucket release announcements, best practices, tips from power users. (how to subscribe?)
Get it free →
Also reporting from Jira? Check out our Excel exporter and PDF exporter apps!