[rt-users] Ticket taken twice

[Joachim Thuau]

aHA!

I didn't get a chance to apply the patch, but we figured out a way to
keep the whole history. The only data that wasn't preserved was the
creation time, but the history is there and valid. That was enough for
us. We created a new ticket, and merged the "broken one" into it. That
transferred all the data (history, requestors, etc) to the new one, but
not the owner. So at this point, we are at a good spot (at least I
think).

I'll work next week on upgrading the setup to the latest and greatest! 
(and I'll report the success...)

Thanks,
Jok

> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com 
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf 
> Of Joachim Thuau
> Sent: Thursday, February 26, 2009 11:35 AM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Ticket taken twice
> 
> 
> I'm a little on the fence about this. I obviously want to 
> "catch up" and get up to 3.8.2 (whoohoo!) but I do need to 
> sort out that ticket first (at least it would make sense...) 
> to make sure it's not going to croak on the reload of the DB. 
> I have looked at the nice relational drawing from the 
> RT-Essential book, and from that I know better than just 
> going into the DB like that and mess with the ticket... I can 
> probably work it out, but I'd love to be able to get to keep 
> that ticket  (well, with the fixed bits in it). Would you 
> share that SQL bits? At least, it'll give me a starting point...
> 
> Thanks,
> Jok