Heya. I was considering changing the rtname variable in config.pm to be a
hash so that each queue can have its own rtname. Is there a reason why
this would be a bad idea (presuming it were a fresh installation without
old ticket correlation issues)?
Regards,
Christian
Christian Gilmore
Infrastructure & Tools Team Lead
Web & Multimedia Development
IBM Software Group
Making RT support multiple ‘virtual’ rtnames wouldn’t be the worst thing
on the planet. I’d probably think about supporting a per-queue rtname
field before just turning rtname into a hash. Once I fork the 2.1
dev tree, I’d consider a patch to do this.
-jOn Wed, Aug 15, 2001 at 12:55:28PM -0500, Christian Gilmore wrote:
Heya. I was considering changing the rtname variable in config.pm to be a
hash so that each queue can have its own rtname. Is there a reason why
this would be a bad idea (presuming it were a fresh installation without
old ticket correlation issues)?Regards,
Christian
Christian Gilmore
Infrastructure & Tools Team Lead
Web & Multimedia Development
IBM Software Group
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
‘“As the company that brought users the Internet, Netscape is now inviting
the more than 60 million people who have used our client software to
‘tune up’ and upgrade to Netscape Communicator,” said Mike Homer,
senior vice president of marketing at Netscape.’ Sometimes I wonder.