Multipe rtname or branded queue with single RT instance?

Looking at the archives, this has been an on again-off again thing for quite a few years. Yes, this is about having the Subject header line contain a queue name or some such identifier, mostly so it “looks nice”. Alas, the Subject heading does play a big role in appearance and thus the buy-in of this from our user population.

I looked at Branded Queue extension, though I’ve not gotten it to work easily with RT-3.6.3 through 3.6.7. If anyone has done so, I’d greatly appreciate a note.

The general recommendation on the list has been to just run multiple instances of RT. That would work, at the expense of duplicating a lot of material. But it’s probably the easiest. We’re evaluating if that’s worth it, just to get this one feature.

However, the preference is for a single instance of a RT database. We don’t mind if the Ticket Number is incremented even though it’s different queues. So English Department #1, and the next ticket might be Physics Department #2 (rather than the first Physics ticket being #1 as well.) That’s fine by us. Nobody’s really keeping track of actual ticket numbering patterns :slight_smile:

So why a single instance? Same set of support staff. So while we’d like the staff of English department to mail english-support@ and get a reply using “Subject English Department Help Desk #x”, and Physics staff members send to physics-support@ and get a reply with “Subject Physics Department Help Desk #x”, it all goes into the same RT system. The actual support staff behind the scenes are the same.

With multiple instances of RT (which I’m guessing involve a separate RT_SiteConfig.pm with $DatabaseName set differently) the staff would have to login to multiple RTs. We’re bound to forget sooner or later.

I was thinking of changing /opt/rt3/lib/RT/Action/SendEmail.pm SetSubjectToken function to change the outgoing Subject. Then using the built-in $EmailSubjectTagRegex to be (English|Physics) Department Help Desk. I’m still not sure about Callbacks, vs Overlays, vs local directory. Or just being old-school and editing the original file directly (at least I understand how that works.)

I’ve not really though through what happens if a ticket moves from the English queue to the Physics queue, but I think it’d still be ok. The ticket number is still unique. And upon receiving the email, RT would still match against both Physics… and English… in the Subject heading.

Tips, advice, warnings, etc welcome.
Thank you,
PH

Paul Hirose : pthirose@ucdavis.edu : Sysadm Motto: rm -fr /MyLife

Looking at the archives, this has been an on again-off again thing
for quite a few years. Yes, this is about having the Subject header
line contain a queue name or some such identifier, mostly so it
"looks nice". Alas, the Subject heading does play a big role in
appearance and thus the buy-in of this from our user population.

I looked at Branded Queue extension, though I’ve not gotten it to
work easily with RT-3.6.3 through 3.6.7. If anyone has done so, I’d
greatly appreciate a note.

You might want to consider RT 3.8, which has the Branded Queues
extension built in…

Isn’t it possible to simply have different templates for different
queues which change the subject title accordingly?

Gordon

With good regexp in the config and 3.6.7 (may be 3.6.6) it’s possible.On Wed, Jul 23, 2008 at 3:58 AM, gordon@cryologic.com wrote:

Isn’t it possible to simply have different templates for different
queues which change the subject title accordingly?

Gordon


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.

Would it be simpler to have an “On Create” scrip which modifies the
ticket subject to add the queue name?

Gordon

Ruslan Zakirov wrote:

Gordon,

Try this in your template:Subject: Request #{$Ticket->Id} in Queue: {$Ticket->QueueObj->Name} has 

been created!

##rest of your template##

Make sure you keep a blank line after the "Subject" header. What we do 

is put the Queue ID and Ticket number AFTER the subject line, like this:

Subject: Request Titled: “{$Ticket->Subject}” has been created!

TICKET INFORMATION:
Queue : {$Ticket->QueueObj->Name}
Number : {$Ticket->Id}
Priority is: {$Ticket->Priority}
Requestor : {$Ticket->Requestors->UserMembersObj->First->Name}
Created by: {$Ticket->CreatorObj->Name}
Created on: {substr($Ticket->Created, 0, 10)}

It's all a matter of how much detail you want to include in a 

notification. ALL of our templates are customized like you see above.
Hope this helps.

Kenn
LBNL