If you want to search for a text value (data type: TEXT) inside a ticket like eg. name of company, country code, city name, project etc. then normally you have to put it between quotation marks. If it’s just one word you don’t have to, you can instead use as described below:

 project:MyFirstCompany

You don’t have to use brackets if it’s one word without spaces. However, when you have spaces between the word, you need to use them:

project:”My first company”

If you want to insert a numeric value (data type: TEXT) like for example the CNI number of a ticket do as follows:

cni:”5″

Also important to know – always try to use the correct spelling for the aliases.

Incorrect spelling

inwarranty:”TRUE”

Correct spelling

inWarranty:”TRUE”

If you want to two or more  values you should use rounded brackets and a connector like AND or OR.

The OR operator displays results with at least one value fulfilled.

affectedCountryCode:(DE OR PL OR GR)

The AND operator displays results with all values fulfilled.

category:(“Break and fix” AND cni.sort:[5 to 8])

If you want to search for a range of tickets you have to use brackets and the word TO as a connector:

appointmentFixedTo:[202105 TO 202110]

The following format is used especially for the date data type fields:

YYYYMMDDHHMM

Year, Month, Day, Hours and Minutes

The shorter format YYYYMMDD or YYYYMM also works for searching

Be advised that searching for ranges only works with the data type date.

If you want to search for a ticket in a specific status you can just use the appropriate alias:

status:canceled

Searching for two status at once:

status: (CANCELED OR “PENDING WAIT ONSITE”)

You can also use NOT to search for specific filter elements according to the exclusion principle:

NOT status: canceled

You can also search for multiple status at once, just use the correct syntax:

NOT status: (CANCELED OR “PENDING WAIT ONSITE” OR APPOINTMENT)

You can use the simple lsdt query to find tickets for a particular date:

lsdt:20210602

If you want to search for tickets within specific dates you can use the time operators YEAR, HOURS, SECONDS and the query NOW to find the ticket:

lsdt:[NOW-1HOUR]

You can also use mathematical symbols to find a particular set of tickets:

lsdt:<20210602

Above alias will search for tickets that were last updated before the 02.06.2021. It will not display tickets after this date.

The following mathematical symbols are supported throughout search fields:

<; >; <=

Let’s say you want to find tickets with the help of mathematical symbols.

What you can do then in this case is to go by the data type date and using for example the alias lsdt to find tickets that are in the Ticket Pool before the LSDT.

lsdt:<=20220601

Absolutely! But just for text and numbers.

Let’s say you want to find tickets with contact persons, where you don’t know the exact spelling. You know the persons’ name starts with a “ki” and ends with a “y”. What you could do in this case is the following:

affectedUser:ki*y

This will display you all tickets with the variation of the name, doesn’t matter if our person is named: Kimchy, Kilaory or Kitty. The search will display them all.

The same principle goes for numbers. Let’s say you don’t know the last digit of the CNI’s so you decide to browse through all of them to find your right ticket.

cni:13*

This will display you all tickets with the CNI numbers between 130 and 139 and the ticket with CNI 13 (because the star doesn’t have to mean a number necessarily).

If you want to search for a ticket with multiple conditions you can use operators as OR, AND; TO or NOT etc. pp.

Be advised that the operator NOT is always put before the alias:

NOT category: “Break and fix”

More complex combined queries:

category:(“Standard” AND appointmentFixedFrom:[202105 TO 202110])

Next example:

category:(“Break and fix” AND cni.sort:[5 to 8])

We currently fully support the following data types in our search.

TEXT: The text data type stores any kind of text data (including numbers).

BOOLEAN: A Boolean value represents a truth value; that is, TRUE or FALSE.

DATE: Date fields have a predetermined size and format. They can be defined on the definition specification. We use the following specification inside our search: YYYYMMDDHHMM or the shorter one YYYYMMDD or YYYYMM

UUID: Universal Unique Identifier, commonly used for unique IDs
(eg. reportingUserId). 

INTEGER: The INTEGER data type stores whole numbers that range from -2147483647 to 2147483647 for 9 or 10 digits of precision.

DOUBLE: A double-precision floating-point number is a long floating-point number of 64 bits.

If you like a query and you want to use it more frequently you can save it for further usage. Find out more in the My queries topic.