The ticket property keywords and their values that you can use in your searches are described in the following table. Not all of the ticket data is searchable. Administrators and agents can search for tickets using these keywords.
Table 1. Searchable ticket properties
There isn't a property keyword for the ticket ID. Instead, you simply search for the ticket by its ID number in the following format:
The date the ticket was created.
The date of the most recent ticket update.
The date the ticket was set to solved.
The due date of tickets with type set to Task.
The assigned agent.
The ticket submitter. This may be different than the requester if the ticket was submitted by an agent on behalf of the requester. You can use the user's name, email address, or the 'me' keyword. See Searching ticket user roles.
The ticket requester.
The text in the ticket's subject.
The text in all the ticket's comments.
New, Open, Pending, Solved, Closed.
Question, Incident, Problem, Task.
Low, Normal, High, Urgent.
The assigned agent's group name.
The name of the ticket requester's organization.
Tags that have been added to the ticket.
The ticket's source, which can be any of the following:
mail (from an email message)
get_satisfaction, get_sat, "get satisfaction" (from Get Satisfaction)
dropbox (from the Zendesk Feedback Tab)
merge (from a ticket merge)
chat (from Chat)
twitter_dm, "twitter dm", "twitter direct" (from a Twitter direct message)
twitter_fav, twitter_favorite, "twitter favorite" (from a Twitter favorite)
twitter (from any Twitter method including direct message and favorite)
Notice that none of these searches required the ID, or name, or email to be explicitly declared. Each of these keywords accepts all of these user identifiers.
Searching for yourself
Themekeyword value allows you to search user properties in tickets where the value is your own user account (as the currently logged in user).
This works for all the user role properties in tickets:
For information about searching for user profile data, see Searching users.
Searching custom ticket fields
You can search for a specific value in custom ticket fields by using the fieldvalue keyword. For example:
This returns all the tickets that have a custom field with the value "12345."
If your custom field assigns a tag to the ticket, you can also search for custom ticket fields using the tags that you assigned to the custom field. For example, if you created a drop-down list, you can search for the tags assigned to each list box item.
To search for specific drop-down list selections, you use the tags keyword.
This applies to the custom field formats that be assigned tags: the drop-down list and the checkbox. The checkbox custom field can include a tag to indicate that the user has clicked the checkbox.
All of the other custom fields (text, multi-line text, numeric, decimal, regular expression) can be searched by the text or number values submitted by ticket requesters. For example, if you added a numeric custom field to the support request form to collect demographic information such as age, you can search for the numbers that the requesters entered in the form (type:ticket "18").
Ordering and sorting ticket search results
Search results can be ordered and sorted using the order_by and sort keywords.
You need to use both of the keywords together in a search statement, as in this example:
status:new order_by:updated_at sort:asc
Here are the valid sorting and ordering keyword and value pairs that you can use:
All of the order_by and sort keyword/values pairs can be used when searching ticket data.