Editing subversion log message does not update 'Repository' view
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.
Updated by Giovani Vizzotto over 14 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 ?
Updated by Anonymous about 14 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).