Makes perfectly sense for me. Additionally it would be cool to include the ticket ID into the commit message. Jira can then associate the changeset with the issue so we can later understand which issue has been fixed by which commit.
For the eclipse users I can recommend the Mylyn plugin which integrates with Jira, takes care of your working contexts and also creates commit comments. It also support working on several tickets in concurrently (you can switch between tasks and mylyn will store/restore your working context (i.e. opened files, optimized autocompletion etc.)... Cheers, Tammo 2007/9/18, Matthieu Riou <[EMAIL PROTECTED]>: > Hi, > > We've taken on the bad habit of fixing stuff without necessarily creating a > Jira task for it. On one side it removes some bureaucracy but on the other > it makes it almost impossible to assemble accurate release notes when we > make releases. So I think we really need that bit of bureaucracy unless > somebody has a better idea. > > Any objection or alternative ideas? (an absence of answer will be considered > a silent agreement and subsequent lapses will require large quantities of > beer as <compensation>) > > Matthieu > -- Tammo van Lessen - [EMAIL PROTECTED] - http://www.taval.de
