So I had intended to get this blog post written a month ago, but since I never got around to it, you get a double-shot of update goodness. I’m happy to announce the release of the Jira Commit Acceptance Plugin version 1.2 and 1.3!
The Commit Acceptance Plugin is a really useful tool for an active development team. As I said in my first post on the subject:

We are heavy users of CVS and Subversion ourselves. Several years ago, when we wanted a better way to tie our version control changes into our Jira issues, we wrote the Jira Subversion Plugin. It auto-magically scans through your commit messages and looks for any issue keys in the message, and then associates issue and the commit in the Version Control Issue Tab.
But that’s really only useful if you remember to put the issue key into your commit message. After a couple of years, we’ve gotten pretty good at this, but everyone still forgets occassionally.
The Commit Acceptance Plugin allows you to prevent developers from committing unless certain, simple conditions are met.

These two recent releases bring a couple of fairly important new features to the Commit Acceptance plugin.
First, you can now associate a repository with multiple Jira projects. You’re no longer constrained to a one-to-one mapping. This is particularly useful for large teams who have lots of separate projects in the Jira and their repository.
And second, we’ve added Perforce client scripts to the plugin, so you can now easily use it with your Perforce source code repository.
Download the new release today and try it out!
I’ll also take the chance to point out that the Commit Acceptance plugin works great with our new product, Fisheye — the best way to look inside source control repository. It works with SVN, CVS and Perforce. There’s also a Fisheye for Jira Plugin that associates issues and commits just like the SVN plugin, but it is even more efficient, and gives you tons of useful graphs and statistics. If you haven’t tried Fisheye yet, give it a shot.

Commit Acceptance Plugin 1.2 1.3