Require Subversion Pre-Commit hook for Comments in JIRA Studio

The following post describes various methods to force commiters to comment their check-in to their SVN repo. How is this possible using JIRA Studio?


3 answers

Right now, JIRA Studio offers one optional pre-commit hook, which requires that the commit comment contains a valid, open issue key:

There aren't any others available right now, but we'd love to hear more about the specific checks you'd like. Please create an improvement request and let us know the details of how you'd like it to work.

Hello Tim,

I was aware of this but this is very limiting. This kind of pre-commit enforces quality that is refelected in FishEye by ensuring comments are entered during a commit. It would seem this feature would only benefit FishEye and JIRA Studio adoption.

Graeme Cloughley
Ravel, Inc. - Director, Software Development

You need to enable editing of commit comments to cope with typos. This is normal subversion stuff.

I've got a user who has committed against the wrong issue number and I can't fix it.

Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

242 views 3 7
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