This isn't so much a feature, as an absolutely essential sanity check that's missing from osTicket:
Please, please, please make sure you check whether certain DB Operations succeed before continuing with the code. The case I found was:
There is no check whether the ticket content could be added to the database before the message is removed from the server.
In my particular case, the messages table got corrupted. By the time I had the time to repair it, a number of tickets were entered without content, and had been deleted off the server.
Please get this fixed in the next release!
