25

We are using Redmine for issue and bug tracking. We added SVN integration but, by doing this, it just shows SVN revisions in activity.

It would be great to see all SVN changes caused by a bug or issue. But it does not seem to be possible.

Is there a way to do that? If not Redmine, which is the best alternative tracking system to achieve this?

German Latorre
  • 10,058
  • 14
  • 48
  • 59

3 Answers3

39

We add the issue number in svn commit message and it's recognized automatically.

svn ci -m "incorrect encoding fixed (refs #2345)"

Later you'll be able to see it in the issue #2345. It doesn't show up right away, I guess redmine checks periodically for repository changes - but if you go to Repository tab and then to the issue, the change should be shown then.

More info about Redmine formatting

==edit==
To answer Jonas comment:

In fact the idea of this is to be able to make connection between some issue and svn revisions related to it. It should work both ways - in repository page you see the link to the issue; in the issue's page you should be able to see the link to the related revisions.

For this to work you need:

  • to have configured repository in your project (or parent project, it works as well)
  • to have configured keywords like refs in Administration->Settings [Repository] ->"Referencing keywords"
  • when you commit to svn (mentioning your issue in commit description like "refs #1234"), this revision doesn't appear automatically in redmine repository - you need to refresh it manually going to Repository tab of the project (it's possible to make it automatic with some cron jobs).

After all this you should be able to see in your issue "Associated revisions"

Dmitry Yudakov
  • 15,364
  • 4
  • 49
  • 53
  • 2
    Awesome reply, thanks! Excellent stuff that Redmine formatting reference, sorry for being such a Redmine-ignorant... – German Latorre Aug 31 '10 at 09:59
  • Regarding Dmitry Yudakovs answer above: As far as I can see, you get a link in the Redmine repository-page to the issue, but there is no way to get a link from the issue to all SVN commits where this issue is referenced. Is there a way to get the link the other way, from issue to SVN commits? – Jonas Dec 08 '11 at 12:30
  • Just maybe you know - what rights should redmine/svn user have to autoclose issues?.. – Andrey Regentov Apr 30 '13 at 09:05
  • @Andrey I haven't tried it, sorry. I guess your svn user should correspond (have the same name or the matching to be configured somehow) to the redmine user that has rights to close issues. – Dmitry Yudakov Apr 30 '13 at 11:58
  • @DmitryYudakov thanks. It appears that my problem with autoclose wasn't related to user permissions. It was custom field "Resolution" that should be filled when autoclose, and it wasn't filled. – Andrey Regentov May 02 '13 at 05:34
8

For posterity:

If the original commit message did not reference a Redmine issue number, you can also do the reverse: manually reference a repository revision by number in a Redmine issue description.

For example:

This issue is an unintended side effect of r5678, which was implemented to address issue #1234.

In that case, "r5678" would automatically link to the revision in Redmine's repository tab (and "#1234" would automatically link to the corresponding issue page).

lx_devr
  • 91
  • 1
  • 2
3

refs allows you to associate a revision to an issue, which is great.

You can also configure another keywords like "fixes" which will associate the revision to an issue, but will also change the status and the % of realisation automatically.

This can be very useful for example when the commit is done to put the issue in a test status. (that will be automatic, without having to do it manually

you can do it administration->settings->repositories and "resolution keywords"

Scavenger
  • 133
  • 2
  • 15
Abdeslem Menacere
  • 91
  • 6