Feature #3533

Editing subversion log message does not update 'Repository' view

Added by Kirill Temnenkov almost 10 years ago. Updated about 8 years ago.

Status:ClosedStart date:2009-06-24
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:-
Resolution:Duplicate

Description

If you make a commit to subversion then update your Redmine 'Repository' view (either by clicking it with autofetch enabled, or running something like

/usr/bin/ruby /home/redmine072/script/runner "Repository.fetch_changesets" -e production

And then subsequently edit the log message for the commit using something like tortoisesvn's edit log message functionality, the updated log message is not detected by Redmine, even after re-running the "Repository.fetch_changesets" script.

In Defect #1577 (http://www.redmine.org/issues/1577#note-4) were written: "Feel free to fill a feature request related to that issue if needed.". I need in this feature


Related issues

Related to Redmine - Defect #1577: Editing subversion log message does not update 'Repositor... Closed 2008-07-04
Duplicates Redmine - Feature #1273: Need a way to re-sync repository history New 2008-05-21

History

#1 Updated by Seth Dziengeleski almost 10 years ago

I've noticed this behavior as well and think this would be a useful feature.

#2 Updated by Giovani Vizzotto almost 10 years ago

I'm having the same problem. I think this is a very useful feature.
In http://www.redmine.org/issues/1577#note-2 were written:

On projects with tens of thousands of revisions, this sounds rather natural not to parse them all because some bits in the log messages may have changed. >If you want to reparse it all, kill it then add it again.
It has been discussed in a previous issue to have a "re-evaluate" facility for automating this process, but I don't know if it eventually lead to an > implementation or not.

There is some way to mannualy kill a revision and add it again ?

#3 Updated by Wayne j over 9 years ago

Just this week someone (me) entered the wrong issue number is a check-in comment. I did some Googling and found something that seems to work. I don't know if it safe. Here's a link to the discussion:

http://www.redmine.org/issues/1273

#4 Updated by Anonymous over 9 years ago

We had the same problem. One of my users forgot to enter the issue number in the comment and since it was already fetched into the database it wasn't detected by redmine after an edit of the log message. So I created a plugin to clear the database from already fetched log messages and recreate them.

You are welcome to check it out...

I'm new to ruby/rails so please try it on a secondary database, I give no guarantees that it doesn't affect anything else. The plugin is available at http://nida.nordenbro.com/redmine/projects/redmine-plrlp/files

Please post enhancements and problems to my tracker (same url).

#5 Updated by Toshi MARUYAMA about 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Duplicate with #1273.

Also available in: Atom PDF