Hi Christian,

Thanks for the answer. I tried all version of the query, but I always got 'No 
matching results.' answers. However, I am pretty sure, that there are tickets 
what would match for these queries:

http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='[email protected]'

or

http://rt_host/rt/REST/1.0/search/ticket?query=Owner='[email protected]'

so, for eg. this is working: 
http://rt_host/rt/REST/1.0/search/ticket?query=Status='new'

The user names and the e-mail addresses are the same, that's why i would expect 
valid answers. My rt version is:  RT 3.8.5

Is this user list query is implemented in this version of this rest api?
Or what do you think I am doing wrong?

Thanks a lot!
Nice weekend.


  Christian Loos <[email protected]>, ezt írta: 
  
  You must use the right field name.
Try this:
http://rt_host/rt/REST/1.0/search/ticket?query=Owner.EmailAddress='[email protected]'

The best way would be to create the search with the query builder and
then copy and paste the query from the advanced tab to the REST url.

-Chris

Am 08.04.2011 08:16, schrieb elekistvan:
> Dear All,
> 
> I would need to use the rest api to query the tickets by e-mail address.
> For eg, something like that: 
> http://rt_host/rt/REST/1.0/search/ticket?query=OWNER.Email='[email protected]'
> Is it possible to query tickets by email via rest api?
> 
> I would need to query these conditions:
> my $tickets = new RT::Tickets($RT::SystemUser);
> ...
> $tickets->FromSQL("(status = 'new' or status = 'open') and  
> (Owner.EmailAddress = '" . $email . "' or Requestor.EmailAddress = '" . 
> $email . "' or Cc.EmailAddress = '" . $email . "' or AdminCc.EmailAddress = 
> '" . $email . "' or Watcher.EmailAddress = '" . $email . "' or 
> QueueCc.EmailAddress = '" . $email . "'  or QueueAdminCc.EmailAddress = '" . 
> $email . "')");
> ...
> 
> If currently this rest api query is not implemented, do you think the 
> solution would be to extend the rest api? 
> for eg: https://gist.github.com/737979
> Is it difficult to do?
> 
> Thanks a lot,
> Steve.
> 
> 

Reply via email to