Wow did I mess up.
Robert Vinson's fork did not have all the methods reproduced, and I didn't
notice. 0.6.0 is almost unusable as a result, if you used anything beyond the
couple of methods implemented there.
I've re-introduced all the missing methods back into 0.6.1 and pushed it.
Please
I have shamelessly and unapologetically stolen Robert Vinson's excellent work
on his fork, for the most part. I did refactor slightly to maintain
compatibility with the previous API, but otherwise it's identical and pushed as
rt-client 0.6.0. It is working for me on ruby 1.9.3p374 on Windows
Tom,
Thanks for the updated rt-client, i will be testing this in the next few weeks.
Thanks,
Eli
On Jul 4, 2013, at 7:05 PM, Tom Lahti tla...@dmsolutions.com wrote:
I have shamelessly and unapologetically stolen Robert Vinson's excellent work
on his fork, for the most part. I did
What is it you are trying to do that isn't working? Looking at the
methods available, it seems they mirror the RT CLI methods:
http://rt-client.rubyforge.org/
So if you want to show a ticket like your example, it seems you would
call rt.show and pass the ticket id.
On 5/4/13 1:33 PM, Peter
Peter,
I had slightly more success with an older version of Ruby and the
rt/client gem. Here's the info from RVM:
ruby-1.8.7-p371 [ i686 ]
I was also encountering problems with manipulating objects despite this.
If you find a solution, there are others interested.
In the interest of
I just pushed version 0.4.0 as a bug fix for 0.3.9
* fixed usersearch method to actually work ^^
* documented usersearch method and added it to the rtxmlsrv.rb XML-RPC service
--
Tom Lahti, SCMDBA, LPIC-1, CLA
BIT LLC
425-251-0833 x 117
RT Training Sessions
I have just pushed rt-client 0.3.9 to rubygems.org.
Changes:
* applied patch from Brian McArdle to deal with spaces in Custom Field names.
* works properly with RT having more than one digit in version strings (e.g. RT
3.8.10)
* new method usersearch, supply a hash with key :EMailAddress to
On Mon, Jan 10, 2011 at 03:57:46PM -0800, Tom Lahti wrote:
I've filed a bug report.
http://issues.bestpractical.com/Ticket/Display.html?id=16418
This is probably the 3rd time its come up. I've discussed it with Jesse on
the RT user's list and he recommended filing a bug report the
It was in something I read somewhere regarding the REST interface. Maybe it
was in the wiki and someone else wrote it.
--
Tom Lahti, SCMDBA, LPIC-1, CLA
BIT LLC
425-251-0833 x 117
I've filed a bug report.
http://issues.bestpractical.com/Ticket/Display.html?id=16418
This is probably the
Surely you remember this thread as well?
http://www.mail-archive.com/rt-users@lists.bestpractical.com/msg28493.html
--
Tom Lahti, SCMDBA, LPIC-1, CLA
BIT LLC
425-251-0833 x 117
On Jan 10, 2011, at 4:27 PM, Tom Lahti wrote:
It was in something I read somewhere regarding the REST interface.
Ah, I know where I got the idea. RT::Client::REST on CPAN uses
Mail::RFC822::Address from CPAN, I believe.
The evilness of spaces in field-names is far less than the one back in October,
with null lines preceeding and after a header in the metadata, which is how the
body is supposed to be
11 matches
Mail list logo
