Online Help | Web App

Using operators in the Filter tab

Updated in 2026

The following tables describe the behavior of operators available on the Filter tab.

Logical operators

These operators are used to combine conditions and groups:

Operator Behavior

And

TRUE if all nested conditions and subgroups return TRUE; otherwise, FALSE.

Or

TRUE if at least one condition or a subgroup returns TRUE; otherwise, FALSE.

Comparison operators

Use the following operators to compose conditions:

Operator Behavior Usage example
is true TRUE if the field value is set to True. Available for Boolean fields only. Active is true
is false TRUE if the field value is set to False. Available for Boolean fields only. Closed is false

equals

TRUE if the field value is equal to any of the specified values.

Category equals Network, Internet, Email

does not equal

TRUE if the field value is not equal to any of the specified values.

Location does not equal Main Office, Western Division

contains

TRUE if the field value contains the specified text; otherwise, FALSE.

Summary contains printer

does not contain

TRUE if the field value does not contain the specified text. Summary does not contain test

is less than

TRUE if the field value is less than the specified one.

Activity Count is less than 3

is less than or equal to

TRUE if the field value is less than or equals to the specified one.

Attachment Count is less than or equal to 2

is greater than

TRUE if the field value is greater than the specified one.

Activity Count is greater than 3

is greater than or equal to

TRUE if the field value is greater than or equals to the specified one.

Attachment Count is greater than or equal 2

like

TRUE if the field value matches the entered text or pattern. % matches any number of characters, _ matches exactly one character. If no wildcards are specified, the value is automatically treated as %value% (similar to contains).

Summary like upgrade%

not like

TRUE if the field value does not match the entered text or pattern. % matches any number of characters, _ matches exactly one character. If no wildcards are specified, the value is automatically treated as %value%.

Summary not like %network%

is blank

TRUE if the field has no value.

Assignee is blank

is not blank

TRUE if the field has a value.

Assignee Group is not blank

Date field filter conditions

For date fields, some conditions use only an operator, while others combine an operator with a selected value, date, date range, or number of days.

All date comparisons account for the client timezone offset.

Filter condition Behavior Usage example
is + relative value

Returns records where the date falls within the selected relative period, such as Today, Yesterday, This week, or Last 30 days.

NOTE: See the full list of relative values below.

Due Date is Today
is equal to TRUE if the field value equals the specified date. Due Date is equal to 04/15/2026
is before TRUE if the field value is earlier than the specified date. Created Date is before 01/01/2026
is after TRUE if the field value is later than the specified date. Resolved Date is after 03/01/2026
is between TRUE if the field value falls within the specified date range. Due Date is between 04/01/2026 and 04/30/2026
is more than TRUE if the field value is more than the specified number of days in the past or future. Created Date is more than 30 days ago
is less than TRUE if the field value is less than the specified number of days in the past or future. Due Date is less than 7 days from now
Relative values

yesterday

TRUE if the field value is equal to the yesterday date. Requires no arguments.

Submit Date is yesterday

today

TRUE if the field value is equal to the current date. Requires no arguments.

Modified Date is today

tomorrow

TRUE if the field value is equal to the tomorrow date. Requires no arguments.

Due Date is tomorrow

in the past TRUE if the field value is earlier than the current date. Requires no arguments. Created Date is in the past
in the future TRUE if the field value is later than the current date. Requires no arguments. Due Date is in the future

this week

TRUE if the field value belongs to the current calendar week. Requires no arguments.

Created Date is this week

this week so far

TRUE if the field value belongs to the current week up to today. Requires no arguments.

Created Date is this week so far

last week

TRUE if the field value belongs to the previous calendar week. Requires no arguments.

Created Date is last week

next week

TRUE if the field value belongs to the next calendar week. Requires no arguments.

Due Date is next week

this month

TRUE if the field value belongs to the current calendar month. Requires no arguments.

Created Date is this month

this month so far

TRUE if the field value belongs to the current month up to today. Requires no arguments.

Created Date is this month so far

last month

TRUE if the field value belongs to the previous calendar month. Requires no arguments.

Submit Date is last month

next month

TRUE if the field value belongs to the next calendar month. Requires no arguments.

Due Date is next month

this quarter

TRUE if the field value belongs to the current quarter. Requires no arguments.

Created Date is this quarter

this quarter so far

TRUE if the field value belongs to the current quarter up to today. Requires no arguments.

Created Date is this quarter so far

last quarter

TRUE if the field value belongs to the previous quarter. Requires no arguments.

Submit Date is last quarter

next quarter

TRUE if the field value belongs to the next quarter. Requires no arguments.

Due Date is next quarter

this year

TRUE if the field value belongs to the current calendar year. Requires no arguments.

Warranty Exp is this year

this year so far TRUE if the field value belongs to the current year up to today. Requires no arguments. Created Date is this year so far
last year TRUE if the field value belongs to the previous calendar year. Requires no arguments. Submit Date is last year

next year

TRUE if the field value belongs to the next calendar year. Requires no arguments.

Lease Return Date is next year

last 7 days TRUE if the field value is within the last 7 days (including today). Created Date is last 7 days
last 14 days TRUE if the field value is within the last 14 days (including today). Invoice Date is last 14 days
last 30 days TRUE if the field value is within the last 30 days (including today). Invoice Date is last 30 days
last 60 days TRUE if the field value is within the last 60 days (including today). Created Date is last 60 days
last 90 days TRUE if the field value is within the last 90 days (including today). Created Date is last 90 days
last 180 days TRUE if the field value is within the last 180 days (including today). Lease Return Date is last 180 days
last 365 days TRUE if the field value is within the last 365 days (including today). Warranty Exp is last 365 days

Multi-value operators

Use these operators with fields that can contain several values, such as tags, groups, categories, or linked items.

Operator Behavior Usage example

has one of

TRUE if the field contains at least one of the specified values.

Tags has one of VIP, Urgent

does not have one of

TRUE if the field is missing at least one of the specified values. This is the opposite of has all of.

Tags does not have one of Archived, Duplicate

has all of TRUE if the field contains all specified values. Tags has all of Hardware, Approved
has none of TRUE if the field contains none of the specified values. Tags has none of Test, Obsolete

User-related operators

Use these operators with person-related fields and related properties.

Operator Behavior Usage example

is current user

TRUE if the field value equals the current user. Available for fields that contain a person.

Requester is current user

is not current user

TRUE if the field value does not equal the current user. Available for fields that contain a person.

Assignee is not current user

is current user organization

TRUE if the field value equals the current user's organization. Organization is current user organization
is not current user organization TRUE if the field value does not equal the current user's organization. Organization is not current user organization
is current user location TRUE if the field value equals the current user's location. Location is current user location

is not current user location

TRUE if the field value does not equal the current user's location. Location is not current user location

Field-to-field comparison

In addition to fixed values, you can compare a field against another field of the same type.

When defining a filter condition, select a dynamic value and choose the field you want to compare with. This allows you to filter records based on relationships between fields.

Examples:

  • Actual Response Date is after Response Date

  • Completed Date is after Due Date

  • Requester equals Assignee

Notes:

  • Both fields must be of the same type (for example, date-to-date or person-to-person).

  • Only direct comparisons are supported. Relative comparisons (such as “3 days later”) are not available.

  • The available operators depend on the field type (for example, date or person fields).