Searching through RT requires some knowledge of how RT does queries. This vignette provides a basic introduction to RT’s query syntax and some examples of how to make queries with this package. Best Practical’s Query Builder documentation and Ticket SQL wiki page highlight some of the key aspects of query-building and are useful to reference while learning.
rt_ticket_search function makes it easy to search through your tickets. These are the fields that it will return by default, and that you can use to search with:
There are additional queryable fields such as
Requestor.Name that you can explore in the Query Builder (Search –> Tickets –> New Search).
These fields are some of the most commonly queried:
To build a query, you’ll want to use the following vocabulary:
ORto join multiple query conditions together
=to specify that a field
!=to specify that a field
is notor is
not equal tosomething
>to specify that a field
LIKEto specify that a field
NOT LIKEto specify that a field
To search for all tickets in the “General” queue, we’d run the following:
<- rt_ticket_search("Queue = 'General'")result
Note that, by default,
rt_ticket_search returns a
tibble (if installed).
You can search against multiple fields using
OR to combine them.
rt_ticket_search("Queue = 'General' AND Subject LIKE 'test'")
Use parentheses to group query parameters together for more advanced logic.
rt_ticket_search("(Status = 'new' OR Status = 'open') AND Queue = 'General'")
For numeric and date/time fields, you can use
<= in addition to
rt_ticket_search("Started > '2018-04-04'")
You can also use special date syntax for more options.
rt_ticket_search("Created >= '2 days ago'")
One of the most common use-cases is searching through RT ticket content. Note that this will only work if your RT installation has full text indexing turned on.
<- rt_ticket_search("Content LIKE 'Can you please advise'")result