Better Commit Policy for Jira (Git, Subversion and more!)

for Jira Server 6.3 - 9.16.1, Jira Data Center 6.3 - 9.17.1 and more
  • Supported
  • Jira Service Management
  • Jira

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

YouTube's thumbnail image for the video.

Work securely with check-in requirements

Verify the commit message, the changed files, the committer, the affected branches and tags before a commit is accepted.

Combine conditions and limit those to branches or directories.

💡 What conditions are supported?

Easy change control, fast code reviews & audits

Implement processes for compliance with industry standards & regulations.

Establish development workflows for consistent repository, code & history.

Enforce traceability between Jira issues and code changes.

💡 How?

For Git, Bitbucket, GitHub, Subversion & Mercurial

Most Version Control Systems and all Operating Systems are supported.

Keep strict quality standards for your production code & data regardless of your environment.

💡 What Version Control Systems?

More details

🛡️ Midori is now SOC 2 compliant!


Better Commit Policy 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.



  • Improved change control over your source code
  • Easier compliance with regulations (story)
  • Faster code reviews
  • Efficient code audits
  • Bi-directional traceability between source code changes and Jira issues
  • Clear commit history

✔️ Available checks:

Supported Version Control Systems:

➕ Connect your VCS, Slack, Twilio, email, CI/CD and custom scripts to Jira workflows with our DevOps automation app!

— Need help?

Privacy and security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy



Manage commit policies centrally in Jira. Commit policies can be specific to one Jira project or can be shared by multiple projects (and multiple VCS repositories) for ultimate flexibility. See: