We had similar requirement and the reason the email interface was not
preferred is because we wanted interaction, immediate visibility of what
in the ticket via the same web form interface .. I opted for a soap
service to create/update and display tickets using soap::lite.
Roy
Stephen Turner wrote:
At Thursday 9/21/2006 09:39 AM, [EMAIL PROTECTED] wrote:
We want to start tracking change request documents in RT. In order
to do
this, we want to create a custom form that has multiple input
textarea boxes
to make sure that we collect all of the necessary information. I'd
like to
massage the data from all of those input boxes and make it the body
of an RT
ticket. What's the best way to go about this without using the RT mail
interface?
Hi Amy,
When you say "custom form" do you mean an addition to RT or a web form
that's on another web server somewhere? If the latter, I'm wondering
why you want to avoid the email interface? Many of our customers have
web forms that send mail into RT and the setup works well for them.
Steve
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
