Jira Service Management Support

This page describes information about operators that are used for advanced searching.

An operator in JQL is one or more symbols or words that compare the value of a field on its left with one or more values or functions on its right. So, only valid results are retrieved by the clause. Some operators may use the NOT keyword.

EQUALS: =

The = operator is used to search for issues where the value of a specified field exactly matches a specified value.

To find issues where the value of a specified field exactly matches multiple values, use multiple EQUALS (=) statements with the AND keyword.

The operator can't be used with text fields. See the CONTAINS operator.

Examples

Find all issues that were created by jsmith:
```
reporter = jsmith
```
Find all issues that were created by John Smith:
```
reporter = "John Smith"
```

^{^top of page}

On this page:

NOT EQUALS: !=

The != operator is used to search for issues where the value of a specified field doesn't match a specified value.

The operator can't be used with text fields. See the DOES NOT MATCH (!~) operator instead.
field != value is the same as NOT field = value.
field != EMPTY is the same as field IS_NOT EMPTY.
The operator won't match a field that has no value (an empty field). For example, component != fred will only match issues that have a component and this component isn't "fred". To find issues that have a component other than "fred" or have no component, you should type component != fred or component is empty.

Examples

Find all issues that are assigned to any user except jsmith:
```
not assignee = jsmith
```
or
```
assignee != jsmith
```
Find all issues that are not assigned to jsmith:
```
assignee != jsmith or assignee is empty
```
Find all issues that were reported by you but aren't assigned to you:
```
reporter = currentUser() and assignee != currentUser()
```
Find all issues where the Reporter or Assignee is anyone except John Smith:
```
assignee != "John Smith" or reporter != "John Smith"
```
Find all issues that aren't unassigned:
```
assignee is not empty
```
or
```
assignee != null
```

^{^top of page}

GREATER THAN: >

The > operator is used to search for issues where the value of a specified field is greater than a specified value.

The operator can only be used with fields that support ordering and can't be used with text fields. For example, date fields and version fields.

To see a field's supported operators, check the individual field reference.

Examples

Find all issues with more than four votes:
```
votes > 4
```
Find all overdue issues:
```
duedate < now() and resolution is empty
```
Find all issues where priority is higher than "Normal":
```
priority > normal
```

^{^top of page}

GREATER THAN EQUALS: >=

The >= operator is used to search for issues where the value of a specified field is greater than or equal to a specified value.

The operator can only be used with fields that support ordering and can't be used with text fields. For example, date fields and version fields.

To see a field's supported operators, check the individual field reference.

Examples

Find all issues with four or more votes:
```
votes >= 4
```
Find all issues due on or after 31/12/2008:
```
duedate >= "2008/12/31"
```
Find all issues created in the last five days:
```
created >= "-5d"
```

^{^top of page}

LESS THAN: <

The < operator is used to search for issues where the value of a specified field is less than a specified value.

The operator can only be used with fields that support ordering and can't be used with text fields. For example, date fields and version fields.

To see a field's supported operators, check the individual field reference.

Examples

Find all issues with less than votes:

votes < 4

^{^top of page}

LESS THAN EQUALS: <=

The <= operator is used to search for issues where the value of a specified field is less than or equal to a specified value.

The operator can only be used with fields that support ordering and can't be used with text fields. For example, date fields and version fields.

To see a field's supported operators, check the individual field reference.

Examples

Find all issues with four or fewer votes:
```
votes <= 4
```
Find all issues that haven't been updated in the last month (30 days):
```
updated <= "-4w 2d"
```

^{^top of page}

IN

The IN operator is used to search for issues where the value of a specified field is one of multiple specified values. The values are specified as a comma-separated list, surrounded by parentheses.

Using IN is equivalent to using multiple EQUALS(=)statements, but is shorter and more convenient. That is, reporter IN (tom, jane, harry) is the same as reporter = "tom" OR reporter = "jane" OR reporter = "harry".

Examples

Find all issues that were created by either jsmith, jbrown, or jjones:
```
reporter in (jsmith,jbrown,jjones)
```
Find all issues where the Reporter or Assignee is either Jack or Jill:
```
reporter in (Jack,Jill) or assignee in (Jack,Jill)
```
Find all issues in version 3.14 or version 4.2:
```
affectedVersion in ("3.14", "4.2")
```

^{^top of page}

NOT IN

The NOT IN operator is used to search for issues where the value of a specified field isn't one of multiple specified values.

Using NOT IN is equivalent to using multiple NOT_EQUALS(!=)statements, but is shorter and more convenient. That is, reporter NOT IN (tom, jane, harry) is the same as reporter != "tom" AND reporter != "jane" AND reporter != "harry".

Also, the NOT IN operator won't match a field that has no value (a field is empty). For example, assignee not in (jack,jill) will only match issues that have an assignee and this assignee isn't "jack" or "jill".

To find issues that are assigned to someone other than "jack" or "jill" or are unassigned, you should type: assignee not in (jack,jill) or assignee is empty.

Examples

Find all issues where the Assignee is someone other than Jack, Jill, or John:
```
assignee not in (Jack,Jill,John)
```
Find all issues where the Assignee isn't Jack, Jill, or John:
```
assignee not in (Jack,Jill,John) or assignee is empty
```
Find all issues where the fix version isn't A, B, C, or D:
```
FixVersion not in (A, B, C, D)
```
Find all issues where the fix version isn't A, B, C, or D, or has not been specified:
```
FixVersion not in (A, B, C, D) or FixVersion is empty
```

^{^top of page}

The IN and NOT IN operators allow using up to 3000 operands.

When the number of operands exceeds the allowed limit, the GET search fails because of the HTTP 400 error on Tomcat. In this case, we recommend using the /search resource through the POST method.

CONTAINS: ~

The ~ operator is used to search for issues where the value of a specified field matches a specified value: either an exact or fuzzy match. See examples below.

Use it only with version and text fields.

Text fields:

Summary
Description
Environment
Comments
Custom fields that use the free text searcher, including custom fields of the following built-in custom field types:
- Free text field (unlimited text)
- Text field (<255 characters)
- Read-only text field

Version fields:

Affected version
Fix version
Custom fields that use the version picker

The JQL field "text", as in text ~ "some words", searches for an issue's summary, description, environment, comments, and all custom text fields.

If you have many text custom fields, you can improve performance of your queries by searching for specific fields. For example: Summary ~ "some words" OR Description ~ "some words".

When using the ~ operator, the value on the right side of the operator can be specified by using Jira text-search syntax.

Examples

Find all issues where the summary contains the word "win" or the simple derivatives of this word, such as "wins":
```
summary ~ win
```
Note that for version fields, the ~ operator returns an exact match. For example, to find the version 9.0, you should use the following query:
```
fixVersion ~ "9.0"
```
Find all issues where the summary contains a wild card match for the word "win":
```
summary ~ "win*"
```
Find all issues where the summary contains the word "issue" and the word "collector":
```
summary ~ "issue collector"
```
Find all issues where the summary contains the exact phrase "full screen". Also, see Search syntax for text fields for details on how to escape quotation marks and other special characters.
```
summary ~ "\"full screen\""
```
With this query, Jira will find issues where the summaries contain both the exact phrase "full screen" and any other phrase that includes the exact word combination "full screen". For example:
- "full screen"
- create "full screen"
- "full screen" editing mode
Find all issues where the Fix Version field contains a wild card match for the version "9". For example, 9.1 or 9.0.1:
```
fixVersion ~ "9*"
```
Find all issues where the Fix Version field contains "9". For example, 1.9:
```
fixVersion ~ "*9"
```

^{^top of page}

DOES NOT CONTAIN: !~

The !~ operator is used to search for issues where the value of a specified field doesn't match a specified value.

Use it only with version and text fields.

Text fields:

Summary
Description
Environment
Comments
Custom fields that use the free text searcher, including custom fields of the following built-in custom field types:
- Free text field (unlimited text)
- Text field (<255 characters)
- Read-only text field

Version fields:

Affected version
Fix version
Custom fields that use the Version Picker

The JQL field "text", as in text !~ "some words", searches for an issue's summary, description, environment, comments, and all custom text fields.

If you have many text custom fields, you can improve performance of your queries by searching for specific fields. For example: Summary !~ "some words" OR Description !~ "some words".

When using the !~ operator, the value on the right side of the operator can be specified by using Jira text-search syntax.

Examples

Find all issues where the summary doesn't contain the word "run" or the derivatives of this word, such as "running" or "ran":
```
summary !~ run
```
Note that for version fields, the ~ operator returns an exact match. For example, to find issues where the fix version is not 9.0, you should use the following query:
```
fixVersion !~ "9.0"
```
This query will return all issues where the value in the Fix Version field isn't 9.0, but it won't return issues where the Fix Version field is empty. To find issues where this field is empty or contains any other value except for 9.0, use the following query:
```
fixVersion !~ "9.0" OR fixVersion is empty
```
Find all issues where the Fix Version field doesn't contain any version from the 9.x line:
```
fixVersion !~ "9.*"
```

^{^top of page}

IS

The IS operator can only be used with the EMPTY or NULL keywords. That is, it's used to search for issues where the specified field has no value.

Not all fields are compatible with this operator. For more details, see the individual field reference.

Examples

Find all issues that have no fix version:
```
fixVersion is empty
```
or
```
fixVersion is null
```

^{^top of page}

IS NOT

The IS NOT operator can only be used with the EMPTY or NULL keywords. That is, it's used to search for issues where a specified field has a value.

Not all fields are compatible with this operator. For more details, see the individual field reference.

Examples

Find all issues that have one or more votes:
```
votes is not empty
```
or
```
votes is not null
```

^{^top of page}

WAS

The WAS operator is used to find issues that currently have or previously had a specified value for a specified field.

In a search query, with this operator, you can use the following:

AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"

The WAS operator will match the value name (for example, "Resolved") that was configured in your system at the time when the field was changed.

The operator will also match the value ID associated with the value name. For example, it will match "4" as well as "Resolved".

The operator can be used only with the following fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status.

Examples

Find issues that currently have or previously had the status "In Progress":
```
status WAS "In Progress"
```
Find issues that were resolved by Joe Smith before February 20:
```
status WAS "Resolved" BY jsmith BEFORE "2011/02/20"
```

Find issues that were resolved by Joe Smith during 2010:

status WAS "Resolved" BY jsmith DURING ("2010/01/01","2011/01/01")

^{^top of page}

WAS IN

The WAS IN operator is used to find issues that currently have or previously had any of multiple specified values for a specified field. The values are specified as a comma-separated list, surrounded by parentheses.

In a search query, with this operator, you can use the following:

AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"

The WAS IN operator will match the value name (for example, "Resolved") that was configured in your system at the time when the field was changed.

The operator will also match the value ID associated with the value name. For example, it will match "4" as well as "Resolved".

Using WAS IN is equivalent to using multiple WAS statements, but is shorter and more convenient. That is, status WAS IN ("Resolved","Closed") is the same as status WAS "Resolved" OR status WAS "Closed".

The operator can be used only with the following fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status.

Examples

Find all issues that currently have or previously had the status "Resolved" or "In Progress":
```
status WAS IN ("Resolved","In Progress")
```

^{^top of page}

WAS NOT IN

The WAS NOT IN operator is used to search for issues where the value of the specified field has never been one of multiple specified values.

In a search query, with this operator, you can use the following:

AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"

Using WAS NOT IN is equivalent to using multiple WAS_NOT statements, but is shorter and more convenient. That is, status WAS NOT IN ("Resolved","In Progress") is the same as status WAS NOT "Resolved" AND status WAS NOT "In Progress".

The operator can be used only with the following fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status.

Examples

Find issues that have never had the status "Resolved" or "In Progress":
```
status WAS NOT IN ("Resolved","In Progress")
```
Find issues that didn't have the status "Resolved" or "In Progress" before February 20:
```
status WAS NOT IN ("Resolved","In Progress") BEFORE "2011/02/20"
```

^{^top of page}

The WAS IN and WAS NOT IN operators allow using up to 3000 operands.

When the number of operands exceeds the allowed limit, the GET search fails because of the HTTP 400 error on Tomcat. In this case, we recommend using the /search resource through the POST method.

WAS NOT

The WAS NOT operator is used to find issues that have never had a specified value for a specified field.

In a search query, with this operator, you can use the following:

AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"

The WAS NOT operator will match the value name (for example, "Resolved") that was configured in your system at the time when the field was changed.

The operator will also match the value ID associated with the value name. For example, it will match "4" as well as "Resolved".

The operator can be used only with the following fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status.

Examples

Find issues that don't have and have never had the status "In Progress":
```
status WAS NOT "In Progress"
```
Find issues that didn't have the status "In Progress" before February 20:
```
status WAS NOT "In Progress" BEFORE "2011/02/20"
```

^{^top of page}

CHANGED

The CHANGED operator is used to find issues where the value of a specified field was changed.

In a search query, with this operator, you can use the following:

```
AFTER "date"
```
```
BEFORE "date"
```
```
BY "username"
```
```
DURING ("date1","date2")
```
```
ON "date"
```
```
FROM "oldvalue"
```
```
TO "newvalue"
```

The operator can be used only with the following fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status.

Examples

Find issues where the Assignee was changed:
```
assignee CHANGED
```
Find issues where the status was changed from "In Progress" back to "Open":
```
status CHANGED FROM "In Progress" TO "Open"
```
Find issues where the priority was changed by the user freddo after the start and before the end of the current week:
```
priority CHANGED BY freddo BEFORE endOfWeek() AFTER startOfWeek()
```

^{^top of page}

Page

Viewport

Confluence

Versions

Advanced searching - operators reference

Advanced searching

On this page

Related content

Still need help?

EQUALS: =

Examples

NOT EQUALS: !=

Examples

GREATER THAN: >

Examples

GREATER THAN EQUALS: >=

Examples

LESS THAN: <

Examples

LESS THAN EQUALS: <=

Examples

IN

Examples

NOT IN

Examples

CONTAINS: ~

Examples

DOES NOT CONTAIN: !~

Examples

IS

Examples

IS NOT

Examples

WAS

Examples

WAS IN

Examples

WAS NOT IN

Examples

WAS NOT

Examples

CHANGED

Examples

Related content