This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!
Security fixes
- Updated dependency: Apache Commons Collections.
This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!
Security fixes
This version introduces a few changes as a preparation for the Jira Server end-of-support.
Important: don't forget that Jira Server will be retired in February 2024!
Improvements
Notable changes
Bugfixes
This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!
Security fixes
This release introduces a handful of features requested by our power users.
New in this release
This version is a compatibility release for Jira 9.
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!).
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
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
Improvements
This version introduces an extended, more flexible security model to ease managing commit policies in large Jira teams.
New in this release
Improvements
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
This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!
Security fixes
This version introduces a few changes as a preparation for the Jira Server end-of-support.
Important: don't forget that Jira Server will be retired in February 2024!
Improvements
Notable changes
Bugfixes
This release introduces security fixes for potential vulnerabilities. We strongly suggest upgrading to this app version as soon as possible!
Security fixes
This release introduces a handful of features requested by our power users.
New in this release
This version is a compatibility release for Jira 9.
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!).
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
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
Improvements
This version introduces an extended, more flexible security model to ease managing commit policies in large Jira teams.
New in this release
Improvements
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
Improvements
Compatibility changes
Bugfixes
New in this release
Improvements
Bugfixes
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:
Improvements:
Bugfixes:
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
Bugfixes
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
Bugfixes
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:
Fixed issue:
After many months of closed beta status, Midori is proud to release this new add-on on Atlassian Marketplace.