What Does IN Mean in a JQL Query?

What IN means in JQL

JQL, or Jira Query Language, is used to search for issues in Jira. The IN operator tests whether a field’s value is one of the values you provide. If any listed value matches, the issue can appear in the results, provided the rest of the query also matches.

For example:

project IN (WEB, MOBILE)

This asks Jira for issues belonging to either the WEB project or the MOBILE project. It does not require an issue to belong to both projects; a single issue has to match one of the listed project values.

Conceptually, this query is similar to:

project = WEB OR project = MOBILE

Using IN is usually easier to read when one field needs to match several alternatives.

How the operator works

The general pattern is a field name, followed by IN, followed by a parenthesized list of values:

field IN (value1, value2, value3)

Jira checks each issue against the list. For a query such as status IN (Open, "In Progress"), an issue matches this condition if its status is Open or In Progress. Other conditions in the query can narrow those results further.

For example:

project = WEB AND status IN (Open, "In Progress")

This returns matching WEB project issues that are in either of the two listed statuses. The AND joins different conditions: the project condition and the status condition must both be true. Within the IN list, the alternatives work like OR.

Use parentheses around the list and separate its entries with commas. Text values containing spaces are commonly enclosed in double quotation marks, as in "In Progress". Jira’s autocomplete and query editor can help identify valid field names and values for your site.

Common examples and useful patterns

IN works with fields that support the relevant comparison, including many single- and multiple-value fields. These examples illustrate common patterns; the exact available values depend on the Jira site and its configuration.

• assignee IN (alice, bob) — issues assigned to either of the listed users.
• priority IN (High, Highest) — issues with either listed priority.
• labels IN (backend, urgent) — issues whose labels match one or more listed labels.
• fixVersion IN ("Release 2", "Release 3") — issues associated with either listed fix version.

Jira’s field types and configuration matter. A field may accept a user, project, version, status, or other kind of value rather than arbitrary text. Use the values that Jira recognizes for that field; a value that looks plausible but is not valid may produce an error or no matches.

IN compared with OR and NOT IN

IN is a compact way to express multiple equality comparisons on the same field. For instance, priority IN (High, Highest) is easier to scan than priority = High OR priority = Highest. The two forms express the same basic alternatives when written with the same field and values.

Use OR when alternatives involve different fields or more complex conditions. For instance, “high priority or assigned to Alice” cannot be expressed as one simple IN list because it checks two different fields.

NOT IN excludes issues with a field value that matches any item in the list. For example:

status NOT IN (Done, Closed)

This excludes issues whose status is Done or Closed. It does not mean “match every value except one particular item in a general sense”; it applies to the named field and the values in that list. How issues with an empty or unset field are handled can depend on the field and query behavior, so test the results rather than assuming that an exclusion also selects empty values.

Choosing values and avoiding errors

Before writing a longer query, identify the field you want to test and verify its accepted values. Field names and displayed values may be customized, and user or project identifiers may need to be entered in a form Jira recognizes. The autocomplete in Jira’s search interface is often useful for checking these choices.

• Keep the list consistent: Each item should be a valid value for the field before IN.
• Quote values with spaces: Use double quotes around values such as "In Progress" or "Release 2".
• Check punctuation: Include opening and closing parentheses, and separate list items with commas.
• Review the logic: A comma-separated IN list means any listed value, not all values at once.
• Use the right field: A valid status value will not work as a project value simply because the spelling is correct.

A frequent misconception is that IN always searches for a word anywhere in an issue. It does not. It compares a particular field to specified values; it is not a general text-search operator. For searching text content, use an appropriate text-search field and operator, such as text ~ "login problem", when supported for the intended search.

Frequently Asked Questions

What does IN do in a JQL query?

It returns issues where the chosen field matches at least one value in the list. For example, project IN (WEB, MOBILE) matches either project.

Is IN the same as OR in JQL?

For several equality checks on the same field, IN is effectively equivalent to joining those checks with OR. It is not a replacement for every use of OR, especially when conditions involve different fields.

How do I exclude multiple values in JQL?

Put NOT before IN, as in priority NOT IN (Low, Lowest). This excludes issues whose priority matches either listed value.

Do JQL IN values need quotation marks?

Values with spaces are commonly enclosed in double quotes, such as "In Progress". Follow Jira’s autocomplete and error messages for the correct format for a particular field and site.

Can I use IN with labels or assignees?

Yes, where the field supports that comparison and the listed values are recognized. Jira configuration and field types can affect which values are accepted.

Related

• How to Get Rid of OneDrive on Windows
• How to Organize a SharePoint Document Library
• Why Do Cats Not Like Water? The Reasons Explained

Further reading: Atlassian Support. Details can change, so check the official page for anything that matters to you. Spotted a mistake? Tell us. How we write an answer.