Hello all,
This week we had a weird problem with RT: a ticket from one queue became
merged with a ticket from another queue, apparently without any user
interaction. No transaction exists for either ticket to suggest that the
merge has been performed, but one ticket’s effective ID has been set to
the other ticket’s ID. Nothing shows up in the logs marking the merge,
although I don’t see any code to log that action in MergeInto().
So, questions: can anyone guess why these tickets might have suddenly
merged? Similarly, can anyone guess why there might not be a transaction
recorded for the merge? And finally, should there be logging to cover
ticket merges? Thanks in advance for all advice and assistance!
Cheers,
Jeff Albert
Hello all,
This week we had a weird problem with RT: a ticket from one queue became
merged with a ticket from another queue, apparently without any user
interaction. No transaction exists for either ticket to suggest that the
merge has been performed, but one ticket’s effective ID has been set to
the other ticket’s ID. Nothing shows up in the logs marking the merge,
although I don’t see any code to log that action in MergeInto().
Well, it should be recording a transaction on merge.
So, questions: can anyone guess why these tickets might have suddenly
merged?
I’ve got to ask: Do any of your coworkers ever touch the database
directly?
Hi Jesse,
One of our groups has read-only access to the database to run some
external tools, but no one is directly updating the database.
Cheers,
Jeff
Jesse Vincent wrote: