force ticket update on refs #ticketNum. To be done when svn commit message is fixed
Added by jmut jmut over 14 years ago
Hi,
Sometimes I mistakenly do ref #num instead of refs #num as a reasult the commit is not mentioned in the ticket.
After this I am fixing the commit message to refs #num but seems redmine is already ignorant to this.
Any approach I can force getting/applying the message in the ticket.
Thanks
Replies (3)
RE: force ticket update on refs #ticketNum. To be done when svn commit message is fixed
-
Added by Felix Schäfer over 14 years ago
Redmine caches the commit messages, so once it has read them, it won't re-read them. The only way to make redmine pick up changes in the commit log is to delete and re-add the repository. You can add ref
as a keyword for the commit logs though, see RedmineSettings.
RE: force ticket update on refs #ticketNum. To be done when svn commit message is fixed
-
Added by jmut jmut over 14 years ago
Thanks.
Btw this is exactly where I read...and I don't see 'ref' mentioned anywhere. 'refs' only.
Cheers
RE: force ticket update on refs #ticketNum. To be done when svn commit message is fixed
-
Added by Felix Schäfer over 14 years ago
You can change what patterns it looks for in the redmine settings. You can even make that it accepts any pattern, i.e. that #id
references a ticket not matter what it has in front of it.