- List Item
VRTS / Znuny used to use 16 digit ticket numbers since the beginning. For a few days there appear 17 digit ticket numbers, which breaks a lot of templates and scripts for permissions handling.
Can we revert to 16 digit numbers?
Description
Description
Related Objects
Related Objects
- Mentioned Here
- T389079: VRT Logons are delayed
Event Timeline
Comment Actions
Examples:
2025031210000737 https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=13518644
20250317104578578 https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=14329439
Comment Actions
Of course templates could be fixed, but this is an unidentified numbers of templates in all wikis, and an unidentified number of gadgets and tools.
Comment Actions
I asked upstream Znuny if there was a recent change about the number of digits used and they said we probably just reached the end of the 6 digit number range.
But your examples don't seem to match that. Right?
Comment Actions
It's been a while since I looked at Znuny/OTRS ticket numbers, but if I remember correctly they were composed of YYYYMMDD and then an 8-digit counter of tickets received that day, resetting at 00:00Z.
Pulling the newest ticket out of the Junk pile, 2025031810009567 was received 03/18/2025 00:11. Paging through the Junk queue, it definitely looks like we got ten thousand tickets in the last 10 minutes. The Mailer Daemon is extremely displeased.
Junk (1000466)
Comment Actions
OMG, you're so right, this is likely all related to too many tickets on one day, which is caused by T389079.
Comment Actions
To be more specific, we use Ticket::Number::DateChecksum setting which the documentation describes as:
With "DateChecksum" the counter will be appended as checksum to the string of date and SystemID. The checksum will be rotated on a daily basis. The format looks like Year.Month.Day.SystemID.Counter.CheckSum (e.g. 2002070110101520, 2002070110101535).