Ticket number reset on upgrade?

[agtcooke]

In version 3.0.10, we changed the ticket numbering from default to auto-increment. Ticket numbers before upgrade were something like 1000075. After upgrading to 3.0.11, I noticed that new tickets started at 1000001. I assume ticket numbers are going to collide.

1) How to correct this?
2) How to avoid it for future upgrades?
3) Is there a preference for the default format (YYYYMMDD########) that ties in here?

We're currently pre-production, and I'm looking forward to going live, but hiccups like this scare me.

Thanks,

Tony

[crythias]

The code for the ticket numbers should and does specifically checks for collision.

[KimmoJ]

I had a very similar experience when I was editing settings, somewhere along the line my ticket numbers got reset. We started out with a simple auto-increment setting that went from 10000 to 10001 etc (the rationale behind that was "easy to read and mention ticket number over the phone or email"), and I was seeing tickets getting created with exactly those numbers, so I changed to a date-based format right then and there just to guarantee that the system wouldn't generate dupes. The date will continue to autoincrement naturally so even if I get the ticket counter reset to zero again, at least it will be (date+01, date+02 etc) rather than just 01, 02...

[agtcooke]

The code for the ticket numbers should and does specifically checks for collision.

Okay great - thanks. Off we go to production...