Ok, so I managed to get RT3 sorted and it is now creating tickets. I
suspected that it was a Postgres problem with RT3, as I was running 7.1.x
I thus migrated sideways to mysql, as this seems to be the preferred DB, and
still had the same error…
Turns out that the req-mailgate was what was bugging me, and I had to set it
to SGID, which resolved that for me.

And our local CPAN doesn’t seem to want to propagate the new
DBIx-SearchBuilder 0.8. Had to manually scrounge it, and install it.

So I also installed RTFM. Two things jumped out at me:
When I search on an RTFM ticket on the reply/comment, it re-adds the
signature. So you end up with multiple signatures in the reply.
I also get the article listed, but when I click on the (GO) button next to
it, it just adds another signature, and no RTFM article… :frowning: Am I missing
something here?

I would also like to be able to use the RTFM Articles as templates on
CREATION of a ticket, not just comment/reply, as I am thinking of using it
to generate a new ticket, and would like to have a default fill-in-form
template that I can edit and whack out, to save a lot of time… How
trivial/non-trivial would it be, to do something like this? Or have a
selection of templates for ticket creation…

Just to outline my thoughts:
The idea is to have an incoming queue, and an outgoing queue. Once an issue
has been analyzed on incoming, I want to create a (new) ticket on outgoing,
which just refers back to the incoming (parent/child). Once the outgoing
issue has been resolved and close, go back to incoming, and reply to the
originator and resolve.
The idea here is that the tickets are separated to prevent accidental
mailing to the originator, as they should not know the outgoing recipient,
yet the outgoing recipient can know who the originator was.
Of course the nice to have would be a “forward” functionality, or a “create
new ticket based on” functionality, which automagically sets the
parent/child relationship…

I have to say again, that this is a great piece of “art”, and I wish I had
more time to tinker with it.

I’m away for the next week, and will catch up on things the week after…

Regards, Jörn Hass
Senior Systems Engineer, Infrastructure.
Internet Solutions
Tel: +27 (11) 575 1000
Fax: +27 (11) 388 3362
E-mail: jorn.hass@is.co.za
WWW: http://www.is.co.za

-> -----Original Message-----
-> From: Jesse Vincent [mailto:jesse@bestpractical.com]
-> Sent: 14 March 2003 23:33 PM
-> To: rt-devel@fsck.com
-> Subject: [rt-devel] Large Sites needed to help test the rt2->rt3
-> migration path
-> I’m looking for a couple of medium-large sites who’d be willing to help
-> test and streamline the RT2 to RT3 migration path. You should have
-> between 25,000 and 200,000 tickets in your RT database. You should have
-> a test host on which you can play with the importer without fear of
-> toasting your live RT instance. Ideally, you should have at least some
-> perl experience to help debug issues we run into. Please contact me at
-> jesse@bestpracctical.com with details about what sort of database you’ve
-> got (Type and version), what sort of host you’ll be doing the testing
-> on and some details about your usage of RT)
-> Thanks,
-> Jesse
-> –
-> http://www.bestpractical.com/rt – Trouble Ticketing. Free.
-> _______________________________________________
-> rt-devel mailing list
-> rt-devel@lists.fsck.com
-> http://lists.fsck.com/mailman/listinfo/rt-devel

"This e-mail may contain confidential information and may be legally
privileged and is intended only for the person to whom it is addressed. If
you are not the intended recipient, you are notified that you may not use,
distribute or copy this document in any manner whatsoever. Kindly also
notify the sender immediately by telephone, and delete the e-mail. When
addressed to clients of the company from where this e-mail originates ("the
sending company “) any opinion or advice contained in this e-mail is subject
to the terms and conditions expressed in any applicable terms of business or
client engagement letter . The sending company does not accept liability for
any damage, loss or expense arising from this e-mail and/or from the
accessing of any files attached to this e-mail.”