
Hello!
We're currently using the DateChecksum module to generate ticket
numbers, but I always felt that the numbers are way too long. As I don't
see any reason for the date or the checksum in the ticket number, I
changed the Random module to generate random _hex_ numbers, 8 digits
long (plus system ID).
Before configuring our system to use the new module, I just wanted to
ask if there are any potential problems here. I've written the
GetTNByString sub to recognize old numbers generated by the DateChecksum
module, as we want to change the module in a live system.
I've attached my module in case anyone finds it interesting. Feel free
to use it.
Thanks,
Frederik
# --
# Ticket/Number/RandomHex.pm - a ticket number random hex generator
# Copyright (C) 2004 Frederik Seiffert

Hi Frederik, On Tue, Jul 27, 2004 at 01:31:28AM +0200, Frederik Seiffert wrote:
We're currently using the DateChecksum module to generate ticket numbers, but I always felt that the numbers are way too long. As I don't see any reason for the date or the checksum in the ticket number, I changed the Random module to generate random _hex_ numbers, 8 digits long (plus system ID).
Before configuring our system to use the new module, I just wanted to ask if there are any potential problems here. I've written the GetTNByString sub to recognize old numbers generated by the DateChecksum module, as we want to change the module in a live system.
If the GetTNByString() is also matching old ticket numbers, then it's no problem. PS: Nice module! :)
Thanks, Frederik
Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

Hi Martin, Martin Edenhofer wrote:
Hi Frederik,
On Tue, Jul 27, 2004 at 01:31:28AM +0200, Frederik Seiffert wrote:
We're currently using the DateChecksum module to generate ticket numbers, but I always felt that the numbers are way too long. As I don't see any reason for the date or the checksum in the ticket number, I changed the Random module to generate random _hex_ numbers, 8 digits long (plus system ID).
Before configuring our system to use the new module, I just wanted to ask if there are any potential problems here. I've written the GetTNByString sub to recognize old numbers generated by the DateChecksum module, as we want to change the module in a live system.
If the GetTNByString() is also matching old ticket numbers, then it's no problem.
I noticed that my GetTNByString() function in my last mail wouldn't match numbers from the DateChecksum module, because it matched the SystemID at the beginning of the ticket number. After removing this, all should work fine.
PS: Nice module! :)
Well, it's mostly based on your work from Random.pm. Feel free to use it or add it to your distribution. You may also remove my copyright at the top. -Frederik

Hi Frederik, On Thu, Jul 29, 2004 at 12:33:06PM +0200, Frederik Seiffert wrote:
Before configuring our system to use the new module, I just wanted to ask if there are any potential problems here. I've written the GetTNByString sub to recognize old numbers generated by the DateChecksum module, as we want to change the module in a live system.
If the GetTNByString() is also matching old ticket numbers, then it's no problem.
I noticed that my GetTNByString() function in my last mail wouldn't match numbers from the DateChecksum module, because it matched the SystemID at the beginning of the ticket number. After removing this, all should work fine.
Oh. Sorry. So if GetTNByString() isn't matching the old foramt, the no email follow up for tickets with old ticket numbers is possible.
PS: Nice module! :)
Well, it's mostly based on your work from Random.pm. Feel free to use it or add it to your distribution. You may also remove my copyright at the top.
Thanks for it Frederik. But I'm not sure what better is. We want to open a http://modules.otrs.org/ section. So (IMO) it would be a very good module for that! :) Would be greate if could put it on there. :)
-Frederik
Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
participants (2)
-
Frederik Seiffert
-
Martin Edenhofer