<p dir="ltr">We use that hook and git-JIRA connection at work. The system will look deep into the messages for the short name. We force branches to also be named after the issue short name as well as including it in commit messages, thus allowing the plug in to find merges related to the issue as well.</p>
<p dir="ltr">--Greg</p>
<div class="gmail_quote">On Mar 16, 2014 8:25 AM, "DM Smith" <<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've just updated the CrossWire tracker (Jira) to hook into Git on GitHub.<br>
<br>
We'll get better issue tracking if we do the following:<br>
Create issues and note the short name of the issue (E.g. JS-224)<br>
When committing in git, use the short name as the prefix of the commit message.<br>
(It actually doesn't have to be a prefix, but I don't know if the connector looks deep into the commit message.)<br>
<br>
Then in Jira you see the commit in the issue.<br>
<br>
In Him,<br>
DM<br>
<br>
<br>
<br>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div>