For those using Eclipse, the linkage between issues & source control can be managed using Mylyn with the JIRA connector: http://confluence.atlassian.com/display/JIRAEXT/Mylyn
Mylyn allows you to specify which issue you are working on, tracks the files you change for that issue, and then commits only those files (with appropriate issue number reference) when you mark the issue as resolved & check in the code. Cheers, Darren >OK. I think those committing code to SVN probably didn't know about using the >JIRA issue id in their log messages. > >Thanks. > >D. > >-----Ursprüngliche Nachricht----- >Von: [email protected] [mailto:[email protected]] Im Auftrag von >Bertrand Delacretaz >Gesendet: Dienstag, 20. Jänner 2009 11:17 >An: [email protected] >Betreff: Re: Why aren't all SVN commits in Jira? > >On Tue, Jan 20, 2009 at 11:02 AM, Hirsch, Richard ><[email protected]> wrote: >> There have been other subversion commits in the SVN trunk (for example, >> Vassil's actions, etc.) but they aren't visible in Jira >> (https://issues.apache.org/jira/browse/ESME?report=com.atlassian.jira.pl >> ugin.ext.subversion:subversion-project-tab). What do we have to do to >> make them appear in Jira as well? > >The link to JIRA does seem to work, as you can see at >https://issues.apache.org/jira/browse/ESME-2 (use the "all" display >option), my http://svn.apache.org/viewvc?view=rev&revision=727325 >commit is visible there. > >Committers must be careful to start their svn log messages with the >JIRA issue id, like "ESME-2 - initial website..." in that example. > >-Bertrand -- [email protected]
