invalid ticket id

[solareon]

I just upgraded from cerberus 2.6 to 4.0. Everything went pretty smoothly and I didn't seem to have any issues until I imported all the tickets from 3.6 to 4.0. After I imported all the tickets I went back to see what tickets were still open and to see how they look.

Almost 95% of the tickets in the database come back with an error saying "invalid ticket id" if I click peek on the ticket it shows up fine. It looks like during the import it didn't create a new mask for the tickets. All the tickets that say "invalid ticket id" have the old mask from 2.6 which started with 50. The new masks have letters in them and those tickets work.

Is there a way to rebuild the ticket ids?

[solareon]

Actually I got it figured out. I just created new masks and replaced the old broken masks and everything worked fine. I dunno if it was just a bug with my import or what happened.

[dsugita]

Alright, glad you were able to get it working. Thanks for updating us on it.

[Hildy]

The problem was likely that the old masks were numeric, and Cerb4 treats a numeric mask as an ID (since the function to get a ticket can take either a numeric ID or a mixed mask).

[solareon]

The problem was likely that the old masks were numeric, and Cerb4 treats a numeric mask as an ID (since the function to get a ticket can take either a numeric ID or a mixed mask).

yeah the weird thing is that some of them got new masks but the old ones stuck. Maybe something to add to the migration tools