How to enforce a JIRA issue to be referenced in a commit message in Subversion

[Jonathan Argue]

I have JIRA 5.1.8, Fisheye 2.8 and Subversion 1.7 installed.

I know that through the use of Subversion pre-commit hooks we can enforce, for example, a commit message to contain text.

I'd like to know how to implement a check to ensure that a valid JIRA issue is included in a commit message when checking in an item into the Subversion repository.

[JamieA · Accepted solution]

Check out the commit acceptance plugin: https://marketplace.atlassian.com/plugins/com.atlassian.jira.ext.commitacceptance

[Midori]

Use the Commit Policy Plugin to verify every aspects of your commits:

• Commit message (minimum length, etc.)
• The identity of the committer (whether he is an active account in JIRA or in a JIRA group)
• Issues referenced in the commit message (whether it mentions an in-progress task, for example)
• Changed files (whether only a specific set of files or file types were committed)

See the documentation

commit-rejected.png