Advanced searching - fields reference

Advanced searching

On this page

Related content

No related content found

This page describes information about fields that are used for advanced searching.A field in JQL is a word that represents a JIRA field (or a custom field that has already been defined in your JIRA applications). In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). The operator compares the value of the field with one or more values or functions on the right, such that only true results are retrieved by the clause.Note, it is not possible to compare two fields in JQL.

Affected version

Search for issues that are assigned to a particular affects version(s). You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).Note, it is better to search by version ID than by version name. Different projects may have versions with the same name. It is also possible for your JIRA administrator to change the name of a version, which could break any saved filters that rely on that name. Version IDs, however, are unique and cannot be changed.

Syntax

affectedVersion

Field Type

VERSION

Auto-complete

Yes

Supported operators

= , != , > , >= , < , <= IS, IS NOT, IN, NOT IN Note that the comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order.

Unsupported operators

~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED

Supported functions

When used with the IN and NOT IN operators, this field supports:

releasedVersions()

latestReleasedVersion()

unreleasedVersions()

earliestUnreleasedVersion()

Examples

Find issues with an AffectedVersion of 3.14:affectedVersion = "3.14"Note that full-stops are reserved characters and need to be surrounded by quote-marks.

Component

Search for issues that belong to a particular component(s) of a project. You can search by component name or component ID (i.e. the number that JIRA automatically allocates to a component).

Note, it is safer to search by component ID than by component name. Different projects may have components with the same name, so searching by component name may return issues from multiple projects. It is also possible for your JIRA administrator to change the name of a component, which could break any saved filters that rely on that name. Component IDs, however, are unique and cannot be changed.

Syntax

component

Field Type

COMPONENT

Auto-complete

Yes

Supported operators

= , != IS , IS NOT , IN , NOT IN

Unsupported operators

~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED

Supported functions

When used with the IN and NOT IN operators, component supports:

componentsLeadByUser()

Examples

Find issues in the "Comp1" or "Comp2" component:component in (Comp1, Comp2)

Find issues in the "Comp1" and"Comp2" components:component in (Comp1) and component in (Comp2)orcomponent = Comp1 and component = Comp2

Created

Search for issues that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Use one of the following formats:

"yyyy/MM/dd HH:mm""yyyy-MM-dd HH:mm""yyyy/MM/dd""yyyy-MM-dd"

Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).

Syntax

created

Alias

createdDate

Field Type

DATE

Auto-complete

No

Supported operators

= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN

Unsupported operators

~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED

Supported functions

When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:

currentLogin()

lastLogin()

now()

startOfDay()

startOfWeek()

startOfMonth()

startOfYear()

endOfDay()

endOfWeek()

endOfMonth()

endOfYear()

Examples

Find all issues created before 12th December 2010:created < "2010/12/12"

Find all issues created on or before 12th December 2010:created <= "2010/12/13"

Find all issues created on 12th December 2010 before 2:00pm:created > "2010/12/12"and created < "2010/12/12 14:00"

Find issues created less than one day ago:created > "-1d"

Find issues created in January 2011:created > "2011/01/01"and created < "2011/02/01"

Find issues created on 15 January 2011:created > "2011/01/15"and created < "2011/01/16"

Creator

Search for issues that were created by a particular user. You can search by the user's full name, ID, or email address.

Syntax

creator

Field Type

USER

Auto-complete

Yes

Supported operators

= , != IS , IS NOT , IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN

Unsupported operators

~ , !~ , > , >= , < , <= CHANGED

Supported functions

When used with the IN and NOT IN operators, this field supports:

membersOf()

When used with the EQUALS and NOT EQUALS operators, this field supports:

currentUser()

Examples

Search for issues that were created by Jill Jones:creator = "Jill Jones"orcreator = "jjones"

Search for issues that were created by the user with email address "bob@mycompany.com":creator = "bob@mycompany.com"(Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

Custom field

Only applicable if your JIRA administrator has created one or more custom fields.

Search for issues where a particular custom field has a particular value. You can search by custom field name or custom field ID (i.e. the number that JIRA automatically allocates to an custom field).

Note, it is safer to search by custom field ID than by custom field name. It is possible for a custom field to have the same name as a built-in JIRA system field; in which case, JIRA will search for the system field (not your custom field). It is also possible for your JIRA administrator to change the name of a custom field, which could break any saved filters that rely on that name. Custom field IDs, however, are unique and cannot be changed.

Customer Request Type

Only applicable if JIRA Service Desk is installed and licensed.

Search for Issues matching a specific Customer Request Type in a service desk project. You can search for a Customer Request Type either by name or description as configured in the Request Type configuration screen.

Note that the Lucene value for Customer Request Type, is portal-key/request-type-key. While the portal key cannot be changed after a service desk portal is created, the project key can be changed. The Request Type key cannot be changed once the Request Type is created.

Supported functions

None

Examples

Find issues where Customer Request Type is Request a new account in projects that the user has access to:"Customer Request Type" = "Request a new account"

Find issues where the Customer Request Type is Request a new account in SimpleDesk project, where the right operand is a selected Lucene value from the auto-complete suggestion list."Customer Request Type" = "sd/system-access"

Find issues where Customer Request Type is either Request a new account or Get IT Help. "Customer Request Type" IN ("Request a new account", "Get IT Help")

Filter

You can use a saved filter to narrow your search. You can search by filter name or filter ID (i.e. the number that JIRA automatically allocates to a saved filter).

Note:

It is safer to search by filter ID than by filter name. It is possible for a filter name to be changed, which could break a saved filter that invokes another filter by name. Filter IDs, however, are unique and cannot be changed.

An unnamed link statement in your typed query will override an ORDER BY statement in the saved filter.

You cannot run or save a filter that would cause an infinite loop (i.e. you cannot reference a saved filter if it eventually references your current filter).

Fix version

Search for issues that are assigned to a particular fix version. You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).

Note, it is safer to search by version ID than by version name. Different projects may have versions with the same name, so searching by version name may return issues from multiple projects. It is also possible for your JIRA administrator to change the name of a version, which could break any saved filters that rely on that name. Version IDs, however, are unique and cannot be changed.

Labels

Search for issues tagged with a label or list of labels. You can also search for issues without any labels to easily identify which issues need to be tagged so they show up in the relevant sprints, queues or reports.

Syntax

labels

Field Type

LABEL

Auto-complete

Yes

Supported operators

= , !=, IS, IS NOT, IN, NOT IN

We recommend using IS or IS NOT to search for a single label, and IN or NOT IN to search for a list of labels.

Unsupported operators

~ , !~ , , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED

Supported functions

None

Examples

Find issues with an existing label:labels = "x"

Find issues without a specified label, including issues without a label:labels not in ("x") or labels is EMPTY

Last viewed

Search for issues that were last viewed on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Use one of the following formats:

"yyyy/MM/dd HH:mm""yyyy-MM-dd HH:mm""yyyy/MM/dd""yyyy-MM-dd"

Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).

Syntax

lastViewed

Field Type

DATE

Auto-complete

No

Supported operators

= , != , > , >= , < , <=IS , IS NOT, IN , NOT IN

Unsupported operators

~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:

currentLogin()

lastLogin()

now()

startOfDay()

startOfWeek()

startOfMonth()

startOfYear()

endOfDay()

endOfWeek()

endOfMonth()

endOfYear()

Examples

Find all issues last viewed before 12th December 2010:lastViewed < "2010/12/12"

Find all issues last viewed on or before 12th December 2010:lastViewed <= "2010/12/13"

Find all issues last viewed on 12th December 2010 before 2:00pm:lastViewed > "2010/12/12"and created < "2010/12/12 14:00"

Find issues last viewed less than one day ago:lastViewed > "-1d"

Find issues last viewed in January 2011:lastViewed > "2011/01/01"and created < "2011/02/01"

Find issues last viewed on 15 January 2011:lastViewed > "2011/01/15"and created < "2011/01/16"

Level

Only available if issue level security has been enabled by your JIRA administrator.

Search for issues with a particular security level. You can search by issue level security name or issue level security ID (i.e. the number that JIRA automatically allocates to an issue level security).

Note, it is safer to search by security level ID than by security level name. It is possible for your JIRA administrator to change the name of a security level, which could break any saved filter that rely on that name. Security level IDs, however, are unique and cannot be changed.

Syntax

level

Field Type

SECURITY LEVEL

Auto-complete

Yes

Supported operators

= , != IS , IS NOT, IN , NOT IN

Unsupported operators

> , >= , < , <= , ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

None

Examples

Search for issues with a security level of "Really High" or "level1":level in ("Really High", level1)

Priority

Search for issues with a particular priority. You can search by priority name or priority ID (i.e. the number that JIRA automatically allocates to a priority).

Note, it is safer to search by priority ID than by priority name. It is possible for your JIRA administrator to change the name of a priority, which could break any saved filter that rely on that name. Priority IDs, however, are unique and cannot be changed.

Syntax

priority

Field Type

PRIORITY

Auto-complete

Yes

Supported operators

= , != , > , >= , < , <= IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Project

Search for issues that belong to a particular project. You can search by project name, by project key or by project ID (i.e. the number that JIRA automatically allocates to a project). In the rare case where there is a project whose project key is the same as another project's name, then the project key takes preference and hides results from the second project.

Syntax

project

Field Type

PROJECT

Auto-complete

Yes

Supported operators

= , !=IS , IS NOT, IN , NOT IN

Unsupported operators

> , >= , < , <= , ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

When used with the IN and NOT IN operators, project supports:

projectsLeadByUser()

projectsWhereUserHasPermission()

projectsWhereUserHasRole()

Examples

Find issues that belong to the Project that has the name "ABC Project":project = "ABC Project"

Find issues that belong to the project that has the key "ABC":project = "ABC"

Find issues that belong to the project that has the ID "1234":project = 1234

Search for issues that were reported by the user with email address "bob@mycompany.com":reporter = "bob@mycompany.com"(Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

Resolution

Search for issues that have a particular resolution. You can search by resolution name or resolution ID (i.e. the number that JIRA automatically allocates to a resolution).

Note, it is safer to search by resolution ID than by resolution name. It is possible for your JIRA administrator to change the name of a resolution, which could break any saved filter that rely on that name. Resolution IDs, however, are unique and cannot be changed.

Syntax

resolution

Field Type

RESOLUTION

Auto-complete

Yes

Supported operators

= , != , > , >= , < , <= IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Unsupported operators

~ , !~

Supported functions

None

Examples

Find issues with a resolution of "Cannot Reproduce" or "Won't Fix":resolution in ("Cannot Reproduce", "Won't Fix")

Resolved

Search for issues that were resolved on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Use one of the following formats:

"yyyy/MM/dd HH:mm""yyyy-MM-dd HH:mm""yyyy/MM/dd""yyyy-MM-dd"

Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).

Syntax

resolved

Alias

resolutionDate

Field Type

DATE

Auto-complete

No

Supported operators

= , != , > , >= , < , <= IS , IS NOT, IN , NOT IN

Unsupported operators

~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:

currentLogin()

lastLogin()

now()

startOfDay()

startOfWeek()

startOfMonth()

startOfYear()

endOfDay()

endOfWeek()

endOfMonth()

endOfYear()

Examples

Find all issues that were resolved before 31st December 2010:resolved <= "2010/12/31"

Find all issues that were resolved before 2.00pm on 31st December 2010:resolved < "2010/12/31 14:00"

Find all issues that were resolved on or before 31st December 2010:resolved <= "2011/01/01"

Find issues that were resolved in January 2011:resolved > "2011/01/01"and resolved < "2011/02/01"

Sprint

Search for issues that are assigned to a particular sprint. This works for active sprints and future sprints. The search is based on either the sprint name or the sprint ID (i.e. the number that JIRA automatically allocates to a sprint).

If you have multiple sprints with similar (or identical) names, you can simply search by using the sprint name — or even just part of it. The possible matches will be shown in the autocomplete drop-down, with the sprint dates shown to help you distinguish between them. (The sprint ID will also be shown, in brackets).

Status

Search for issues that have a particular status. You can search by status name or status ID (i.e. the number that JIRA automatically allocates to a status).

Note:

It is safer to search by status ID than status name. It is possible for your JIRA administrator to change the name of a status, which could break any saved filter that rely on that name. Status IDs, however, are unique and cannot be changed.

The WAS, WAS NOT, WAS IN and WAS NOT IN operators can only be used with the name, not the ID.

Syntax

status

Field Type

STATUS

Auto-complete

Yes

Supported operators

= , != IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Unsupported operators

~ , !~ , > , >= , < , <=

Supported functions

None

Examples

Find issues with a status of "Open":status = Open

Find issues with a status ID of 1:status = 1

Find issues that currently have, or previously had, a status of "Open":status WAS Open

Type

Search for issues that have a particular issue type. You can search by issue type name or issue type ID (i.e. the number that JIRA automatically allocates to an issue type).

Note, it is safer to search by type ID than type name. It is possible for your JIRA administrator to change the name of a type, which could break any saved filter that rely on that name. Type IDs, however, are unique and cannot be changed.

Syntax

type

Alias

issueType

Field Type

ISSUE_TYPE

Auto-complete

Yes

Supported operators

= , !=IS , IS NOT , IN , NOT IN

Unsupported operators

~ , !~ , > , >= , < , <=WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

None

Examples

Find issues with an issue type of "Bug":type = Bug

Find issues with an issue typeof "Bug" or "Improvement":issueType in (Bug,Improvement)

Updated

Search for issues that were last updated on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Use one of the following formats:

"yyyy/MM/dd HH:mm""yyyy-MM-dd HH:mm""yyyy/MM/dd""yyyy-MM-dd"

Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).

Syntax

updated

Alias

updatedDate

Field Type

DATE

Auto-complete

No

Supported operators

= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN

Unsupported operators

~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:

currentLogin()

lastLogin()

now()

startOfDay()

startOfWeek()

startOfMonth()

startOfYear()

endOfDay()

endOfWeek()

endOfMonth()

endOfYear()

Examples

Find issues that were last updated before 12th December 2010:updated < "2010/12/12"

Find issues that were last updated on or before 12th December 2010:updated < "2010/12/13"

Find all issues that were last updated before 2.00pm on 31st December 2010:updated < "2010/12/31 14:00"

Find issues that were last updated more than two weeks ago:updated < "-2w"

Find issues that were last updated on 15 January 2011:updated > "2011/01/15" and updated < "2011/01/16"

Find issues that were last updated in January 2011:updated > "20011/01/01" and updated < "2011/02/01"

Voter

Search for issues for which a particular user has voted. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for your own votes. See also votedIssues.

Syntax

voter

Field Type

USER

Auto-complete

Yes

Supported operators

= , !=IS , IS NOT , IN , NOT IN

Unsupported operators

~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Supported functions

When used with the IN and NOT IN operators, this field supports:

membersOf()

When used with the EQUALS and NOT EQUALS operators, this field supports:

currentUser()

Examples

Search for issues that you have voted for:voter = currentUser()

Search for issues that the user "jsmith" has voted for:voter = "jsmith"

Search for issues for which a member of the group "jira-administrators" has voted:voter in membersOf("jira-administrators")

Watcher

Search for issues that a particular user is watching. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for issues where you are the watcher. See also watchedIssues.