I’m expanding my RT install to include a 2nd queue. In testing it looks
like the new tickets in that queue are number sequentially with the old
queue. I searched archives and found an old post from 2001 stating this is
by design. (Carbon60: Cloud Consulting - Services and Solutions) Has
8 years of development changed this?
Z
I’m expanding my RT install to include a 2nd queue. In testing it looks
like the new tickets in that queue are number sequentially with the old
queue. I searched archives and found an old post from 2001 stating this is
by design. (Carbon60: Managed Cloud Services) Has
8 years of development changed this?
No. Ticket # is still a globally incrementing counter. If it were not,
email messages would have to include both the ticket # and queue name.
Cambridge Energy Alliance: Save money. Save the planet.
too bad, I would have like the option to keep them seperate.
I’m no programmer but it seem to me a easy method to implement would be to
number tickets with que#.ticket# (01.1056). I believe qu eues are given a
unique number after they are created.
Thanks.On Fri, Jan 22, 2010 at 3:49 PM, Jerrad Pierce < jpierce@cambridgeenergyalliance.org> wrote:
On Fri, Jan 22, 2010 at 16:45, Aaron Zuercher aaron.techgeeks@gmail.com wrote:
I’m expanding my RT install to include a 2nd queue. In testing it looks
like the new tickets in that queue are number sequentially with the old
queue. I searched archives and found an old post from 2001 stating this
is
by design. (Carbon60: Managed Cloud Services)
Has
8 years of development changed this?
No. Ticket # is still a globally incrementing counter. If it were not,
email messages would have to include both the ticket # and queue name.
–
Cambridge Energy Alliance: Save money. Save the planet.