WebService for RT?

RT Users
1

Has anyone ever written a webservice or something to remotely create and
update tickets? I have a few ideas where I need an external system to check,
create and update RT tickets.

I have done this in the past with the SSH and local scripts, but I would
rather not have to do that with this solution.

Thanks for you suggestions or help!

2

Thanks. This looks like a good solution, however I need something that
can give me back the Ticket ID and other information immediately.
Having to wait for an email reply from RT to confirm the changes, etc
would not be ideal.

Thanks!On Feb 19, 2009, at 7:30 AM, Kobus Bensch - No Sig wrote:

Hi

Enable and use the commands by email option.

Kobus

3

Chris Black wrote:

Thanks. This looks like a good solution, however I need something that
can give me back the Ticket ID and other information immediately.
Having to wait for an email reply from RT to confirm the changes, etc
would not be ideal.

The REST interface just gives you the information back immediately
if you don’t count HTTP roundtrip time.

Regards
Racke

LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

4

Chris Black wrote:

Has anyone ever written a webservice or something to remotely create and
update tickets? I have a few ideas where I need an external system to
check, create and update RT tickets.

I have done this in the past with the SSH and local scripts, but I would
rather not have to do that with this solution.

There is a REST interface and a corresponding Perl module (though that
might be a bit outdated with 3.8).

Regards
Racke

LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

5

There is a REST interface and a corresponding Perl module (though that
might be a bit outdated with 3.8).

I’m using RT::Client::REST against 3.8.2 just fine.

6

Jesse Vincent wrote:

There is a REST interface and a corresponding Perl module (though that
might be a bit outdated with 3.8).

I’m using RT::Client::REST against 3.8.2 just fine.

I’m also right now working on a ruby class that does essentially the same thing.

Using RT::Client::REST (or my ruby class when its finished) it should not be
hard to wrap the whole API in an XML-RPC service, or something similar, if you
really wanted to. Though the wisdom of making a web service that accesses
another web service would definitely be questioned. I suppose its likely that
if you are using, say, classic ASP, that XML-RPC access to RT::Client::REST
might be a far shade easier to code than re-writing RT::Client::REST in ASP.

If I can get permission to open source my ruby class, I will.

– ============================
Tom Lahti
BIT Statement LLC

http://www.bitstatement.net/
– ============================

7

There is a REST interface and a corresponding Perl module (though that
might be a bit outdated with 3.8).

I’m using RT::Client::REST against 3.8.2 just fine.

Including access to Custom Fields? IIRC the current RT::Client::REST
release doesn’t handle the new 3.8 style naming convention yet.
Patches are in RT though…

Drew
Drew Taylor * Web development & consulting
Email: drew@drewtaylor.com * Site implementation & hosting
Web : www.drewtaylor.com * perl/mod_perl/DBI/mysql/postgres

8

I’m using RT::Client::REST against 3.8.2 just fine.

Including access to Custom Fields? IIRC the current RT::Client::REST
release doesn’t handle the new 3.8 style naming convention yet.

Yep. I could believe that there might be issues with escaping and very
oddly named CFs, which, IIRC, was what we’ve fixed in recent RT but none that I’ve hit.