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

    Learn more

    for Jira Server 6.2 - 7.6.1 and more versions
    Versions available for Jira Server 6.1 - 6.1.9
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Midori Global Consulting Kft. supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    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-committed.

    PRODUCT OVERVIEW - USER MANUAL

    Benefits:

    • 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/

    Reviews for cloud

    (8)
    Sign in to write a review
    by Tindur Hafsteinsson on 2017-08-29
    A must have plugin if you want to kick-off some CI/CD initiatives using the Atlassian Products. Took me just few minutes to install and then configure my first rule, and it simply worked, and I was able to enforce the minimum requirements for our CI/CD workflow to work. The challenge with implementing robust automation in development is to ensure all rules are followed. In our case, we branch per story, and upon merge after review, our code is automatically built, various tests executed, including vulnerability scans, and finally our new container is deployed into K8S clusters. We use the JIRA issuekey as the identifier, thus we must be able to enforce that all commits are done in reference with the correct issue, in the correct project. And that's exactly what the Commit Policy Plugin does for us. Furthermore, I can ensure in a simple, but powerful way, who can commit into my repositories (in my case the developer must be JIRA user - where JIRA uses our AD user directory). What I liked here, since I had to put restrictions on my developers, the plugin didn't force me to change how my developers want to interact with the repositories, - in command line, in Bitbucket, in JIRA, in any type of git clients. It also allowed me to provide my developers with intuitive feedback - guidance how they should e.g. form their smart commits in cases the commit rule blocked them from committing.
    Was this review helpful?YesNo
    by Kasi Bade on 2017-08-02
    This is very much helpful to my requirement. We have so much customization to check conditions before promoting the code to Bitbucket. This one Plugin take cares of everything. I will strongly recommand this for everyone who has customizations like me.
    Was this review helpful?YesNo
    by Sean Miller on 2017-05-18
    Love this tool. Very handy for keeping commits linked to JIRA tickets.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Yakov Yukhnovetsky on 2017-04-05
    At the beginning, I thought "WTF ??? Why do I need it ? It's just yet another do-it-in-my-boss-way", but after playing a little bit more with JCP configuration an policies, I realized, that we must use it as an instrument for keeping the configuration management discipline. I mean, not all the software developers are well organized creatures (like me :-)). JCP plugin helps keep our GIT repository well commented and stick to Jira tasks and issues. Well, guys, it is not so terrible as it seems to be, and I really believe, every software company must incorporate it into its developing process.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Midori Global Consulting Kft.

    "... every software company must incorporate it into its developing process."

    Great summary. We couldn't agree more with this. Thanks, Yakov!

    by Eric FOUCHER on 2017-02-13
    This is a must have to have a clean repository. The ability to check the rules also locally is just great. The support team is really reactive and efficient. Good job for a great plugin
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for server

    (8)
    Sign in to write a review
    by Tindur Hafsteinsson on 2017-08-29
    A must have plugin if you want to kick-off some CI/CD initiatives using the Atlassian Products. Took me just few minutes to install and then configure my first rule, and it simply worked, and I was able to enforce the minimum requirements for our CI/CD workflow to work. The challenge with implementing robust automation in development is to ensure all rules are followed. In our case, we branch per story, and upon merge after review, our code is automatically built, various tests executed, including vulnerability scans, and finally our new container is deployed into K8S clusters. We use the JIRA issuekey as the identifier, thus we must be able to enforce that all commits are done in reference with the correct issue, in the correct project. And that's exactly what the Commit Policy Plugin does for us. Furthermore, I can ensure in a simple, but powerful way, who can commit into my repositories (in my case the developer must be JIRA user - where JIRA uses our AD user directory). What I liked here, since I had to put restrictions on my developers, the plugin didn't force me to change how my developers want to interact with the repositories, - in command line, in Bitbucket, in JIRA, in any type of git clients. It also allowed me to provide my developers with intuitive feedback - guidance how they should e.g. form their smart commits in cases the commit rule blocked them from committing.
    Was this review helpful?YesNo
    by Kasi Bade on 2017-08-02
    This is very much helpful to my requirement. We have so much customization to check conditions before promoting the code to Bitbucket. This one Plugin take cares of everything. I will strongly recommand this for everyone who has customizations like me.
    Was this review helpful?YesNo
    by Sean Miller on 2017-05-18
    Love this tool. Very handy for keeping commits linked to JIRA tickets.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Yakov Yukhnovetsky on 2017-04-05
    At the beginning, I thought "WTF ??? Why do I need it ? It's just yet another do-it-in-my-boss-way", but after playing a little bit more with JCP configuration an policies, I realized, that we must use it as an instrument for keeping the configuration management discipline. I mean, not all the software developers are well organized creatures (like me :-)). JCP plugin helps keep our GIT repository well commented and stick to Jira tasks and issues. Well, guys, it is not so terrible as it seems to be, and I really believe, every software company must incorporate it into its developing process.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Midori Global Consulting Kft.

    "... every software company must incorporate it into its developing process."

    Great summary. We couldn't agree more with this. Thanks, Yakov!

    by Eric FOUCHER on 2017-02-13
    This is a must have to have a clean repository. The ability to check the rules also locally is just great. The support team is really reactive and efficient. Good job for a great plugin
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Pricing

    10 users$1025 users$19050 users$390100 users$790250 users$1290500 & upAdditional pricing details

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps 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 app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app 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?

    Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products 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 apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

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

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

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

    Can I extend my free trial?

    For server apps, you can extend your app 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 app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps 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 app pricing is no longer available. You have two options for app purchasing:

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

    Learn more

    Midori Global Consulting Kft. is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 2.4.0 Jira Server 6.2 - 7.6.1 Released 2017-11-21

    Summary

    Compatibility release for Jira 7.6.

    Details

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

    Installation

    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 app 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 apps