
Duarte, I think you are going to run into problems using the same ticket numbers over and over again as time progresses. One suggestion I have would be to change your System ID annually to prefix with the year, then you could successfully reset the starting ticket number in the TicketCounter.Log file (I think) or you could simply change over to the DateChecksum method. In scenario 1 your tickets would be 200500001 if you choose a 5 digit MinCounterSize In scenario 2 your ticket numbers would be 2005091607163400001 If you don't want to change your system ID or your ticket numbering method then my suggestion would be to export your database (MySQL?) into a sql script and edit out the ticket related fields and subsequently reimport the data after dropping and recreating the database. (Don't forget the permissions grants) I hope this helps Brad West Network/Systems Engineer Spang & Company bwest@spang.com mailto:bwest@spang.com _____ From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Duarte Cordeiro Sent: Friday, September 16, 2005 6:17 AM To: User questions and discussions about OTRS.org Subject: [otrs] Ticket number generator reset Hi, Yesterday we've created with our ticket number 19000. Adding this to our system id (that I wrongly choose as 10), we have a ticket numbers like 1019000. I would like to reset this number every year, so what I would like to know is: - if I change the number in TicketCounter.log do the ticket numbering restart ? - Is there any implication to this ? Does otrs stops working correctly? What happens if a user reply to a ticket number that exists twice in the database? Thanks, Duarte Cordeiro