This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!

See the full release notes →

This release introduces a handful of features requested by our power users.

New in this release

• "... must contain issue keys" type conditions support the issues moved between projects.
• Configurable "Did you mean?".

See the full release notes →

This version is a compatibility release for Jira 9.

See the full release notes →

This version fixes a major bug in 5.0.0 that would affect the upcoming Better DevOps Automation for Jira app (coming soon, fingers crossed!).

See the full release notes →

This version prepares the foundation for a new Midori app called Better DevOps Automation for Jira.

Note that when upgrading from 4.3.0 to 5.0.0, there is no visible change in the Better Commit Policy app's already existing functionality. But, under the hood, it implements the API that will power the upcoming DevOps automation app.

Improvements

• Support for DevOps automations, provided by the upcoming Better DevOps Automation for Jira app.

See the full release notes →

This version comes with improved guides for Bitbucket Server, Bitbucket Data Center, Bitbucket Cloud, GitHub, GitHub Enterprise, GitLab CE/EE and GitLab.com. Additionally, it introduces several new features: "did you mean?" intelligent issue key suggestions, cloning commit policies and bypassing complete changesets and single commits by commit messages and committers.

New in this release

• Improved guides for Bitbucket Server, Bitbucket Data Center, Bitbucket Cloud, GitHub, GitHub Enterprise, GitLab CE/EE and GitLab.com.
• "Did you mean?" (intelligent issue key suggestions).
• Clone commit policy.
• Bypassing complete changesets and single commits by commit messages and committers.

Improvements

• New REST API end-point to clone policies programmatically.

See the full release notes →

This version introduces an extended, more flexible security model to ease managing commit policies in large Jira teams.

New in this release

• Extended security model (in nutshell: project administrators can manage policies!).

Improvements

• New "Getting Started" page.
• Sharing the hook script package with your peers is explicitly discouraged in the hook script wizard UI (to avoid a common mistake).

See the full release notes →

This version is a compatibility release for the Jira 8 line.

As you probably know, Better Commit Policy already supports Jira Data Center deployments (i.e. clustered Jira). To be precise, those are supported since app version 1.4.0 (released in Jan 2016).

In 2018, Atlassian re-launched its Data Center program and introduced new testing criteria for "Data Center approved apps". This version is the official release for the revised program, tested to live up to the rigorous demands of Data Center environments.

New in this release

• "Commit Policy Plugin for Jira" is now called "Better Commit Policy for Jira"!
• Better Commit Policy is a Data Center approved app!

This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!

See the full release notes →

This release introduces a handful of features requested by our power users.

New in this release

• "... must contain issue keys" type conditions support the issues moved between projects.
• Configurable "Did you mean?".

See the full release notes →

This version is a compatibility release for Jira 9.

See the full release notes →

This version fixes a major bug in 5.0.0 that would affect the upcoming Better DevOps Automation for Jira app (coming soon, fingers crossed!).

See the full release notes →

This version prepares the foundation for a new Midori app called Better DevOps Automation for Jira.

Note that when upgrading from 4.3.0 to 5.0.0, there is no visible change in the Better Commit Policy app's already existing functionality. But, under the hood, it implements the API that will power the upcoming DevOps automation app.

Improvements

• Support for DevOps automations, provided by the upcoming Better DevOps Automation for Jira app.

See the full release notes →

This version comes with improved guides for Bitbucket Server, Bitbucket Data Center, Bitbucket Cloud, GitHub, GitHub Enterprise, GitLab CE/EE and GitLab.com. Additionally, it introduces several new features: "did you mean?" intelligent issue key suggestions, cloning commit policies and bypassing complete changesets and single commits by commit messages and committers.

New in this release

• Improved guides for Bitbucket Server, Bitbucket Data Center, Bitbucket Cloud, GitHub, GitHub Enterprise, GitLab CE/EE and GitLab.com.
• "Did you mean?" (intelligent issue key suggestions).
• Clone commit policy.
• Bypassing complete changesets and single commits by commit messages and committers.

Improvements

• New REST API end-point to clone policies programmatically.

See the full release notes →

This version introduces an extended, more flexible security model to ease managing commit policies in large Jira teams.

New in this release

• Extended security model (in nutshell: project administrators can manage policies!).

Improvements

• New "Getting Started" page.
• Sharing the hook script package with your peers is explicitly discouraged in the hook script wizard UI (to avoid a common mistake).

See the full release notes →

This version is a compatibility release for the Jira 8 line.

As you probably know, Better Commit Policy already supports Jira Data Center deployments (i.e. clustered Jira). To be precise, those are supported since app version 1.4.0 (released in Jan 2016).

In 2018, Atlassian re-launched its Data Center program and introduced new testing criteria for "Data Center approved apps". This version is the official release for the revised program, tested to live up to the rigorous demands of Data Center environments.

New in this release

• "Commit Policy Plugin for Jira" is now called "Better Commit Policy for Jira"!
• Better Commit Policy is a Data Center approved app!

Improvements

• More efficient computation of the "is existing" property for Git commits.

Compatibility changes

• To take advantage of the improvement, the required Git version is 2.11.0. (But, older Git versions are still supported!)

See the full release notes →

Bugfixes

• Fixed: Subversion hook script fails to find branches and tags with Python 3.

See the full release notes →

New in this release

• Branch verification
• Tag verification
• New option for commit policies: "Accept existing commits without verification"
• New option for commit policies: "Accept merge commits without verification"
• New condition: "Changed paths (files) must contain issue keys from a JQL query"
• New option for issue key verifying conditions: "Allow additional issue keys in commit messages" (plus branch names, tag names)

Improvements

• Git branch names are now simply "feature/my-branch" (previous app versions used the refspec format like "refs/heads/feature/my-branch").
• Automatic hook script version checks are executed to find outdated hook scripts.
• Console output format was significantly extended (but also streamlined at the same time!) to display problems related to branches and tags.
• ... and more!

Bugfixes

• Fixed: Only the first line of multi-line Git commit messages are processed.

See the full release notes →

This version is a compatibility release for the Jira 7.6 line.

This version is a compatibility release for the Jira 7.4 line.

This version is a compatibility release for the Jira 7.3 line.

This version is primarily a compatibility release for the Jira 7.2 line, but also includes a couple of improvements around evaluating the "commit message must contains issue keys" condition.

Improvements:

• JQL warnings and errors raised while executing the search will be displayed by the VCS client. (In previous versions, the commit was correctly rejected, but the root cause appeared only in the server logs.)
• When the JQL is empty, formally correct, but non-existing issue keys will be rejected. (In previous versions, "FOOBAR-123" was always accepted by empty JQLs. This is now accepted only if it actually exists.)

Improvements:

• JQL conditions are evaluated faster and using less memory, particularly in Jira instances with tens or thousands of hundreds of issues

Bugfixes:

• No more ClassCastException is thrown during condition evaluations, in environments using Crowd for user management
• When JQL conditions are evaluated, user name is printed instead of user key (i.e. user account renames are handled in the expected way)
• VCS usernames are allowed to contain '@' characters

Token-based authentication

This new authentication mode, based on security tokens instead of plain text passwords, greatly improves hook security.

Git client-side verifications (commit-msg hook)

Reject broken commits before those are actually made! This mechanism verifies the commits in the developers' clone at commit time.

Support for Bitbucket Cloud & GitHub

Verify commits locally even if the remote repository is hosted in a closed system, where you cannot configure hooks.

Hook Script Wizard

The redesigned interface makes hook script installation a breeze.

"$committer.userName" variable

This variable in JQL conditions will be replaced with the committer's username before the JQL search is executed. Example JQL: "assignee = $committer.username"

Improvements

• Execute permission "x" is auto-set for hook script files (on U*X)

Bugfixes

• VisualSVN permission problems fixed
• All condition types obey file path based scope limiting
• International character fixes on Windows (files and usernames)

Support for Jira Data Center

In a clustered Jira environment, commit policies and global settings are transparently replicated among the nodes by the add-on. Using the the "load balanced" Jira URL in the hook scripts, you can achieve high availability in the hooks, as well. Therefore, the add-on fully supports Jira enterprise deployments.

Changes

• JQL condition accepts empty an JQL string, to ease the "any valid issue key without further filtering" use case.

Bugfixes

• Textual commit condition parameters (ex: JQL queries) that contain international characters are correctly encoded.

This release extends the Jira compatibility range to 6.1 - 7.0.

It also introduces new REST API integration points primarily designed for our next add-on (will be released in the next few weeks!).

This release is compatible with the the Jira 7 line.

There are no functional changes in this release.

This version is compatible with any Jira version between (and including) 6.1.0 and 6.4.x.

As a usability improvement, we made the display of evaluation results more intuitive for multi-condition rules using the "OR" logical operator. Instead of listing all conditions as "failed" for each commit, we display only those that should actually be fixed by the committer.

This version has been verified with Jira 6.2.x, 6.3.x and 6.4x releases, supporting all modern Jira versions. (We will be looking into supporting Jira 6.1.x soon.)

This version additionally fixes a SQL query problem (case sensitivity of column names).

There are no functional changes.

We are happy to announce that Commit Policy Plugin for Jira is now ready for production use. Starting from this version, Midori offers commercial support also for this product.

This version introduces support for the Mercurial version control system, in addition to Subversion and Git.

Finally, this version implements the following checks:

• Committer must have a valid Jira account and must be in a Jira group
• Committer username or email must match a pattern
• Commit message must match a pattern
• Commit message must contain issue keys from a JQL query
• Changed files must match a pattern

Fixed issue:

• A naming collision with another Jira plugin disabled the "Global configuration" screen in certain installations. It works fine now.

After many months of closed beta status, Midori is proud to release this new add-on on Atlassian Marketplace.