Customers have installed this add-on in at least 132 active instances.
    by Midori Global Consulting Kft.Atlassian Verified
    Midori Global Consulting Kft. is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 6.2 - 7.2.3 and more versions
    Versions available for JIRA Server 6.1 - 6.1.9
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Midori Global Consulting Kft. supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Verify the changes committed to Git, Bitbucket, GitHub, GitLab, Subversion & Mercurial against configurable rules

    Verify the changes committed to Git, Bitbucket, GitHub, GitLab, Subversion & Mercurial against configurable rules

    Powerful check-in requirements

    Consistent workflow, repository & code

    For Git, Subversion, Mercurial, Bitbucket & GitHub

    Verify the committer person, the commit message and the changed files before the commit is accepted.

    Combine multiple parametric and scope-limited conditions with AND/OR operators.

    ☛ What conditions are supported?

    Establish development workflows and good practices.

    Restrict committing to specific users, user groups, etc.

    Enforce traceability between JIRA issues and code changes.

    Lock repositories, directories, files.

    Most major VCS systems on all OS are supported. (More coming!)

    Use the add-on even while transforming from Subversion to Git!

    REST API to integrate in custom environments.

    ☛ What Version Control Systems?

    More details

    Commit Policy Plugin checks the changes committed to your Version Control System against a set of configurable rules (the commit policy). When the policy is not satisfied, the commit is rejected. Rejected commits can then be "fixed" and re-commited.



    • Bidirectional traceability from source code changes to user stories, tasks, bugs or other issue types
    • Well-organized repositories and source code
    • Clear commit history
    • Conventions & good practices
    • Controlled processes

    Available conditions (can be combined with AND/OR):

    Supported Version Control Systems:

    Using the legacy Commit Acceptance Plugin? Here is the comparison.

    — Need some help? https://midori.zendesk.com/

    User reviews

    Sign in to write a review »
    by Kalen Brown on 2016-05-05
    While the plugin is great, the support is even greater (shout out to Gabor)! The plugin seemed to work well out of the box for GIT, but I had initial issues with SVN. All my issues with SVN were solved within a couple of days and the fixes were rolled into released versions so I can keep upgrading like normal. I think this plugin is great for security but also just for a helpful reminder to follow process if even your own internal made up process. I see many applications for many reasons. The initial environment setup was fairly easy, and I think with the latest changes to the plugin will make it even more transparent. Just set it and forget it. With their latest version, it is possible for non JIRA admins to deploy the hook scripts of already created policies. So if a user decides they like a policy, they could deploy it themselves into their GIT or SVN repository without having to bug an admin (although deployment should be notified to an admin). I think this is an interesting new feature.
    Was this review helpful?YesNo

    Midori Global Consulting Kft.

    Thanks for the kind words, Kalen.

    The primary use case for the revamped self-service Hook Script Wizard is that you are now able to generate "pre-commit" type hooks to your local Git repositories. We don't know any other product offering this feature, and this makes commit validation super-fast and -powerful.

    by Julian Phillips on 2016-04-19
    Not only does this plugin provide exactly the features we were looking for (the ability to restrict commits to specific Subversion branches to selected issues in Jira), it was easy to setup with clear instructions for installing the Subversion hook scripts. Had a slight issue getting things working, but support was great - extremely helpful, responsive, and polite.
    Was this review helpful?YesNo
    by Bart Dubelaar on 2015-06-10
    Great plugin, way better than the old commit acceptance plugin. This plugin provides multiple features from the top of our own Jira whish-list: * Ability to confine code commits to issues in the current sprint * Ability to confine code commits to subtasks only (keeping all commits related to issues on the agile board) * User configurable regex to match for issue keys in commit messages. (we can now use "-" in our commits again) The plugin generates the required hook scripts for you (tested for SVN). Very nice feature.
    Was this review helpful?YesNo

    Midori Global Consulting Kft.

    Thanks, Bart!

    Be prepared for more awesomeness coming soon, including additional condition types and better support for Git and Mercurial.


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    Midori Global Consulting Kft. is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Midori Global Consulting Kft. supports Commit Policy for JIRA (Git, SVN, Hg). You can visit the support site to get help.

    Get support


    Version 2.1.0 JIRA Server 6.2 - 7.2.3 Released 2016-09-02


    Compatibility release for JIRA 7.2. More precise execution of JQL searches.


    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.


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


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Commit Policy for JIRA (Git, SVN, Hg) via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Commit Policy for JIRA (Git, SVN, Hg). You're prompted to log into MyAtlassian. Commit Policy for JIRA (Git, SVN, Hg) begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Commit Policy for JIRA (Git, SVN, Hg) versions compatible with your instance, you can look through our version history page.

    Similar add-ons