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?
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.
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.
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
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
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