On Fri, Apr 24, 2015 at 3:18 PM, Kristen <[email protected]> wrote: > Hi, > > Using RabbitVCS, I committed changes for a particular trac ticket but > added the wrong ticket # in the message of the changeset. Now the > changeset message is under the wrong ticket in Trac. Is there a way using > RabbitVCS or trac to move the changeset message from, for example, ticket > #42 to #44. > > For example, in the comments section of trac: > > In 19100/exampleproject: > > Refs #42: Updated the code > > Needs to be changed to: > > Refs #44: Updated the code > > Thanks for your help! > > Kristen >
Are you using Subversion? If you are using Subversion and have a post-revprop-change hook configured to allow log message editing, and the post-revprop-change hook also calls "trac-admin changeset modified", then the comment will be added to the new ticket when you edit the Subversion log message. I don't remember what the behavior is for the old ticket comment, but I think the message changes to "the changeset doesn't reference this ticket". The ticket comment can change because the content of the message is a call to the CommitTicketReferenceMacro. You could delete the old comment using TracAdmin or the TicketDeleter component. http://trac.edgewall.org/wiki/TracRepositoryAdmin#Subversion - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
