Commit Policy Plugin for Jira

Verify the changes committed to Git, Bitbucket, GitHub, GitLab, Subversion & Mercurial against configurable rules
How does it work?

Commit Policy Plugin checks the changes committed to your Version Control System against a set of configurable rules (the commit policy).

When the rules are not satisfied, the commit is rejected. Rejected changes should be "fixed" to comply with the rules, and then be re-committed.

Why should I use commit policies?

As a result of enforcing rules on the changes submitted your Version Control System, the quality of your processes, the traceability of your changes and the consistency of your source code dramatically improve.

Learn more by watching the intro video in the left.

Work securely with check-in requirements

The rules can verify every aspect of the changes: the commit message, the changed files, the committer, the affected branches and tags.

Each rule:

  • can be limited to specific branches or directories
  • can combine multiple conditions with AND/OR
  • can show custom instructions to the developer when his/her commit is rejected
No extra efforts

Commit Policy Plugin is the only commit checker app for the Atlassian platform that verifies commits before those are created! With "broken" commits effectively prevented, no efforts are wasted to fix those. Find out why →

Quick adoption

Let's face it: developers hate (and refuse) heavy-weight processes. Albeit being light-weight, Commit Policy Plugin prevents chaos and encourages good practices that everyone agrees upon. And it does so without losing agility.

Works with your current tools

Your team members can use any standard-compliant VCS client (command-line, GUI tools, IDE integrations) on any Operating System.

Zero learning curve

After a couple of rejections, clean and precise commits become the new normal.

Verify the tags in your repositories
Verify the branches your developers create
  • Branch name must match a pattern
    • branch names must be one of the types "feature/*", "release/*" or "maintenance/*"
    • bugfix branch names must contain a test execution ID like "bugfix/1741"
  • Branch name must contain issue keys from a JQL query
    • story branch names must include a "Story" type issue from the currently running Scrum sprint like "story/CAL-123-shared-calendars"
    • bugfix branch names must include an unresolved "Bug" type issue assigned to the committer
Enforce useful commit messages
  • Commit message must contain issue keys from a JQL query
    • no changes accepted without at least one Jira issue associated
    • changes must refer to exactly one user story in the current sprint
    • changes must refer to unresolved bugs and change requests planned for the next maintenance version of project FOOBAR
  • Commit message must match a pattern
    • commit messages must be at least 10 characters long (excluding whitespace)
    • commit messages must start with a Jira issue key
Control the file additions / deletions / modifications
Who is who and who can do what?

Rigorous change control

Establish processes for compliance with ISO standards, IEC standards and industry regulations in:

  • defence
  • financial
  • avionics (success story)
  • automotive
  • medical
  • pharmaceutical
  • other safety-critical systems

Or, just make sure that every change to your code is introduced in a controlled and documented way!

End-to-end traceability

Accelerate requirements validation, compliance verification, impact analysis, coverage analysis and source code audits by bi-directionally linking Jira issues and source code changes:

  • requirements ⇔ code changes
  • epics ⇔ user stories ⇔ code changes
  • tasks / bugfixes ⇔ code changes
  • tests ⇔ code changes
  • change requests ⇔ sub-tasks ⇔ code changes
  • releases ⇔ issues ⇔ code changes

Faster code reviews & audits

Maintain development workflows for consistent repository, code & history.

By making small improvements (useful tips) in the way your team works, common questions like these will be automatically answered:

  • "Why was this changed?"
  • "Was it tested? In what environments?"
  • "Is this within the scope of the current release?"
  • "Who approved this merge?"
  • "Is there a programmatic test for this story?"

Who's using it?

I really believe, every software company must incorporate it into its developing process.

Yakov Y., Philips

This is a must have to have a clean repository. The ability to check the rules also locally is just great.

Eric F., CTA International

What I liked here, 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.

Tindur H., KORTA

Not only does this plugin provide exactly the features we were looking for, it was easy to setup with clear instructions. Support was great - extremely helpful, responsive and polite.

Julian P., Roke

While the plugin is great, the support is even greater (shout out to Gabor)! The initial environment setup was fairly easy. Just set it and forget it.

Kalen B., EaglePicher Technologies
more reviews →

Evaluation: try before you buy

  1. Install the app. (how to install?)
  2. Get your free trial license that allows using the app without limitations for 30 days. (how to try?)
  3. When the trial is over, continue using the app by purchasing a commercially supported license. (how to buy?)
  4. Ask questions or report problems any time by clicking the "Help" tab in the right bottom. (how to get support?)
  5. Get the latest Commit Policy Plugin release announcements, best practices, tips from power users in email (how to subscribe?)
Try it free →
Also reporting from Jira? Check out our Excel exporter and PDF exporter apps!