One thing I meant to mention as well is the following ‘asymmetrical’ behavior:
Once the Watcher list is set up via RT Web interface, then it is ok to conduct collaborative communication via email – with the caveat that only the RT-queue email address is the email recipient and the Subject line contains the ‘[rt-queue #123]’ (or something like that) tag.
Again, as far as people who are collaborating on a particular RT request are concerned, email replies should be sent to RT queue email address only. RT server is the one that will forward the email mesg to the people on the Watcher list for that ticket.
It’s kinda weird that you have to manage Watcher list via RT Web interface, the but actual communication amongst the people can be done either via the web interface or email. It would be nice if I can do all that via email, but I don’t think it’s possible (without some heavy hacking made to RT).
It’s kinda weird that you have to manage Watcher list via RT Web
interface, the but actual communication amongst the people can be
done either via the web interface or email. It would be nice if I can
do all that via email, but I don’t think it’s possible (without some
heavy hacking made to RT).
I’m not sure I think it is all that weird: if you think of RT as a
‘brilliant’ mailing list manager (which is what you’re sort of using it
as in that environment), then setting up groups through the web sounds
less weird.
I still think there might be a way to have the RT mail intake code to
look for In-Reply-To Message-ID, though.
Cheers,
– jra
Jay R. Ashworth jra@baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
If you can read this... thank a system adminstrator. Or two. --me