name change doesn't clear trunk_id



name change doesn't clear trunk_id+issues

If you take a plus card (A+B) and rename it to "C", then it still thinks its "trunk" is A and tag is B. Or something like that (see example)

This may be the underlying problem to several other renaming tickets...



Found this one because of extra cards (the searches) showing up in Ticket+*plus_cards. Evidently they were originally named Ticket+(whatever) and then changed to High Priority Tickets, etc.


New example:


Created a basic card+a card it is plussed to and renamed it to a renamed card. Sure enough:



Can't reproduce this.  Let's get a concrete example or close it.

The old example seemed okay, but i did a new one just to be sure. See above. --John Abbe

  --John Abbe.....Mon Dec 08 00:11:54 -0800 2008

This was actually pretty easy. Simple test, simple unintrusive fix. The only part I'm a little concerned about is the migration, which relies on a find_by_sql. If there's a better way to do it I'm all ears.

  --Ethan McCutchen.....Fri Dec 19 11:36:55 -0800 2008