The ticket number, that appears on the subject line, should
be fixed number of digits with left zeroes. Otherwise
email sorts #1,#10,#100,#1000 before #2,#20,#200,#2000
and so on. Isn’t this what people really want: #0001, #0002, #0010, #0020, #0100, #0200, #1000, #2000?
First __THEY__ came for Elian, and I did nothing.
When __THEY__ came for me, there was no one left.
<a class='attachment' href='/uploads/db7930/original/1X/00ae80e65e135231d03ac4adc3b256433ca5abb8.vcf'>saint.vcf</a> (1.51 KB)
The problem with that is that every RT instance I’ve seen has scaled
past the point it was initially designed for. What happens when you hit
5 digits. With 2.x, we should have apropriate in-reply-to headers, so
date + threads should work…which will help somewhat.
jOn Tue, Jul 18, 2000 at 11:00:49AM -0500, Dan St.André wrote:
The ticket number, that appears on the subject line, should
be fixed number of digits with left zeroes. Otherwise
email sorts #1,#10,#100,#1000 before #2,#20,#200,#2000
and so on. Isn’t this what people really want: #0001, #0002, #0010, #0020, #0100, #0200, #1000, #2000?
--
==============================================================
First __THEY__ came for Elian, and I did nothing.
When __THEY__ came for me, there was no one left.
=============================================================
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
“Mary had a crypto key / She kept it in escrow
And everything that Mary said / The Feds were sure to know” – Sam Simpson
The ticket number, that appears on the subject line, should
be fixed number of digits with left zeroes. Otherwise
email sorts #1,#10,#100,#1000 before #2,#20,#200,#2000
and so on.
If it’s a problem, there is one very quick workaround; put in a dummy
request in RT with serial_num 10000. Then the following requests will be
numbered 10001, 10002, … 11234, etc. Works all until you hit #99999 …
