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

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.

2 answers

1 accepted

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published 5 hours ago in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

71 views 4 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you