If you're using the default ticket numbering with time stamp, this shouldn't be a problem (date/time also uniquely identifies a ticket). If you're using a 4 digit autoincrement or alternative (random?) numbering scheme, that might be different. What numbering scheme are you using?
On Thu, Jan 13, 2011 at 2:17 AM, Sune T. Tougaard <[email protected]>wrote: > Hi list, > > > > I’ve seen this issue a few times, and i’m not quite sure what happens. > > > > Back in November, I sent a mail to this list named “Autoincrement trouble” > where I explained how my TicketIDs had started from scratch. > > > > This appears to have happened again (and again). > > > > I’m running 2.4.7 on a Windows 2008 R2 installation, and looking at the > “otrs\var\log\ticketcounter.log” the number in there matches what the otrs > system uses. > > However, looking at the “Previous Versions” of this file, it seems as if > it’s jumping a bit back and forth. > > > > For example, some day last week, it said “5879” and 6 hours later it said > “3094”. > > > > Can anyone explain to me what the purpose of ticketcounter.log is and what > may cause this behavior? > > > > I do not want my otrs to start over with the Ticket IDs every other week, > but I’m still not sure what happens. > > Can anyone help? Thanks. > > > > -- > > Kind regards > > /Sune T. > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
