Advanced search reference - JQL fields | Jira Service Management Cloud | Atlassian Support (2023)

Table of Contents
Affected version Approvals Assignee Attachments Category Change gatingtype Component Created Creator Custom field Customer Request Type Description Due Environment Epic link Filter Fix version Issue key Issue link Issue link type Labels Last viewed Level Organization FAQs Videos

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 anoperator, which in turn is followed by one or more values (orfunctions). 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 twofields 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 TypeVERSION
Auto-completeYes
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=and!=operators, this field supports:

  • latestReleasedVersion()
  • earliestUnreleasedVersion()

When used with theINandNOT INoperators, this field supports:

  • releasedVersions()
  • unreleasedVersions()
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.
  • Find issues with an AffectedVersion of "Big Ted":
    affectedVersion = "Big Ted"
  • Find issues with an AffectedVersion ID of 10350:
    affectedVersion = 10350

^ top of page

Approvals

Used inJira Service Managementonly.

Search for requests that have been approved or require approval. This can be further refined by user.

Syntax
approvals
Field TypeUSER
Auto-complete

No

Supported operators

=

Unsupported operators

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

Supported functions
  • approved()
  • approver()
  • myApproval()
  • myPending()
  • myPendingApproval()
  • pending()
  • pendingBy()
Examples

  • Find requests that require or required approval by John Smith:
    approvals = approver(jsmith)

  • Find requests that require approval by John Smith:
    approvals = pendingBy(jsmith)

  • Find requests that require or have required approval by the current user:
    approvals = myPending()

  • Find all requests that require approval:
    approvals = pending()

^ top of page

Assignee

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

Syntax
assignee
Field TypeUSER
Auto-complete

Yes

Supported operators

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

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 ~ , !~ , > , >= , < , <=
Supported functionsWhen used with theINandNOT INoperators, this field supports:
  • membersOf()

When used with theEQUALSandNOT EQUALSoperators, this field supports:

  • currentUser()
Examples

  • Find issues that are assigned to John Smith:
    assignee = "John Smith"
    or
    assignee = jsmith

  • Find issues that are currently assigned, or were previously assigned, to John Smith:
    assignee WAS jsmith

  • Find issues that are assigned by the user with email address "bob@mycompany.com":
    assignee = "bob@mycompany.com"

    Note that full-stops and "@" symbols are reserved characters and need to be surrounded by quote-marks.

^ top of page

Attachments

Search for issues that have or do not have attachments.

Syntax
attachments
Field TypeATTACHMENT
Auto-completeYes
Supported operatorsIS, IS NOT
Unsupported operators=, != , ~ , !~ , > , >= , < , <= IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functionsNone
Examples

  • Search for issues that have attachments:
    attachments IS NOT EMPTY

  • Search for issues that do not have attachments:
    attachments IS EMPTY

^ top of page

Category

Search for issues that belong to projects in a particular category.

Syntax
category
Field TypeCATEGORY
Auto-completeYes
Supported operators =, !=
IS, IS NOT, IN, NOT IN
Unsupported operators~ , !~ , > , >= , < , <=WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functionsNone
Examples

  • Find issues that belong to projects in the "Alphabet Projects" Category:
    category = "Alphabet Projects"

(Video) Using JIRA's advanced search, JQL

^ top of page

Change gatingtype

Used in Jira Service Managementonly.

Search for types of change gating that are used in change requests. "Tracked-only" requests are produced by integrations that stand separately from a change management process. These tools don't respect approval or change gating strategies. Change requests that are "tracked-only" are just for record-keeping purposes.

Syntax
change-gating-type
Field TypeTEXT
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 requests where the gating type is empty:
    change-gating-type is EMPTY
  • Find requests where the gating type is tracked-only:
    change-gating-type = "tracked-only"

^ top of page

See Also
15 Strategies for Quickly Expanding Your Business6 Data Quality Issues in Reporting and Best Practices to Overcome Them | Databox BlogTop 12 Free/Open source Document Management System Software 2021Project Manager Resume Examples

Search for issues that have a comment that contains particular text.Jira text-search syntaxcan be used.

Syntax
comment
Field TypeTEXT
Auto-complete

No

Supported operators

~ , !~

Unsupported operators= , != , > , >= , < , <=
IS, IS NOT, IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functionsNone
Examples
  • Find issues where a comment contains the words "My PC is quite old":
    comment ~ "\"My PC is quite old"

^ top of page

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 tosearch 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 TypeCOMPONENT
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)
    or
    component = Comp1 and component = Comp2
  • Find issues in the component with ID 20500:
    component =20500

^ top of page

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 TypeDATE
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"

^ top of page

Creator

Search for issues that were created by a particular user.You can search by the user's full name, ID, or email address. Note that an issue's creator does not change, so you cannot search for past creators (e.g. WAS). SeeReporterfor more options.

Syntax
creator
Field TypeUSER
Auto-complete

Yes

Supported operators

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

Unsupported operators~ , !~ , > , >= , < , <=
CHANGED, WAS, WAS IN, WAS NOT, WAS NOT IN
Supported functions

When used with theINandNOT INoperators, this field supports:

  • membersOf()

When used with theEQUALSandNOT EQUALSoperators, this field supports:

  • currentUser()
Examples
  • Search for issues that were created by Jill Jones:
    creator ="Jill Jones"
    or
    creator = "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 reservedcharacters, so the email address needs to be surrounded by quote-marks.)

^ top of page

Custom field

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

(Video) JIRA Tutorial #28 - Searching issues with JQL functions

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

Note, it is safer to search by custom fieldID than by custom fieldname.It is possible for a custom fieldto 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 fieldIDs, however, are unique and cannot be changed.

Syntax
CustomFieldName
Alias
cf[CustomFieldID]
Field TypeDepends on the custom field's configuration

Note, Jira text-search syntaxcan be used with custom fields of type 'Text'.

Auto-complete

Yes, for custom fields of type picker, group picker, select, checkbox and radio button fields

Supported operators

Different types of custom field support differentoperators.

Supported operators:
number and date fields

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

Unsupported operators:
number and date fields		~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported operators:
picker, select, checkbox
and radio button fields		= , !=
IS , IS NOT , IN , NOT IN
Unsupported operators:
picker, select, checkbox
and radio button fields		~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported operators:
text fields		~ , !~
IS , IS NOT
Unsupported operators:
text fields		= , != , > , >= , < , <=
IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported operators:
URL fields

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

Unsupported operators:
URL fields		~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

Different types of custom fields support differentfunctions.

Supported functions:
date/time fields

When used with theEQUALS,NOT EQUALS,GREATER THAN,GREATER THAN EQUALS,
LESS THANorLESS THAN EQUALSoperators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
Supported functions:
version picker fields		Version picker fields: When used with theINandNOT INoperators, this field supports:
  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
Examples
  • Find issues where the value of the "Location" custom field is "New York":
    location ="New York"
  • Find issues where the value of the custom field with ID 10003 is "New York":
    cf[10003] ="New York"
  • Find issues where the value of the "Location" custom field is "London" or "Milan" or "Paris":
    cf[10003] in ("London","Milan","Paris")
  • Find issues where the "Location" custom field has no value:
    location != empty

^ top of page

Customer Request Type

Used in Jira Service Managementonly.

Search for requests of a certain request type. You can search by request type name or request type description as configured in the Request Type configuration screen.

Syntax
"Customer Request Type"
Field TypeCustom field
Auto-complete

Yes

Supported operators
= , !=

IN , NOT IN

Unsupported operators

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

Note that the Lucene value for Customer Request Type, isportal-key/request-type-key. While the portal key cannot be changed after a service project 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")

^ top of page

Description

Search for issues where the description contains particular text.Jira text-search syntaxcan be used.

Syntax
description
Field TypeTEXT
Auto-complete

No

Supported operators

~ , !~
IS , IS NOT

Unsupported operators= , != , > , >= , < , <=
IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
Supported functions

None

Examples
  • Find issues where the description contains the words "Please see screenshot":
    description ~"Please see screenshot"
See Also
We Analyzed 4 Million Google Search Results. Here's What We Learned About Organic CTRTop 9 document management systems for law firms — Avokaado Blogكمبوند المقصد ريزيدنس العاصمة الإدارية Al Maqsad Residence11 Essential Podcasts for Operations Managers | Hubble

^ top of page

Due

Search for issues that were due on, before, or after a particular date (or date range). Note that the due date relates to thedateonly (not to the time).

Use one of the following formats:

"yyyy/MM/dd"
"yyyy-MM-dd"

Or use"w"(weeks) or"d"(days) to specify a date relative to the current date. Be sure to use quote-marks (").

Syntax
due
Alias
dueDate
Field TypeDATE
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 theEQUALS,NOT EQUALS,GREATER THAN,GREATER THAN EQUALS,
LESS THANorLESS THAN EQUALSoperators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
Examples
  • Find all issues due before 31st December 2010:
    due <"2010/12/31"
  • Find all issues due on or before 31st December 2010:
    due <="2011/01/01"
  • Find all issues due tomorrow:
    due ="1d"
  • Find all issues due in January 2011:
    due >="2011/01/01"and due <="2011/01/31"
  • Find all issues due on 15 January 2011:
    due ="2011/01/15"

^ top of page

Environment

Search for issues where the environment contains particular text.Jira text-search syntaxcan be used.

Syntax
environment
Field TypeTEXT
Auto-complete

No

Supported operators

~ , !~
IS , IS NOT

Unsupported operators= , != , > , >= , < , <=
IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
Supported functions

None

Examples
  • Find issues where the environment contains the words "Third floor":
    environment ~"Third floor"

^ top of page

Epic link

Search for issues that belong to a particular epic in company-managedprojects. The search is based on either the epic's name, issue key, or issue ID (i.e. the number that Jira automatically allocates to an issue).

To search for issues that belong to a particular epic in team-managed projects, use parent.

(Video) 4.2 Advanced Search with Confluence Query Language - CQL - Confluence Data Center/Server
Syntax
"epic link"
Field TypeEpic Link Relationship
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 theINorNOT INoperators,epic linksupports:

  • issueHistory()
  • linkedIssues()
  • votedIssues()
  • watchedIssues()
Examples
  • Find issues that belong to epic "Jupiter", where "Jupiter has the issue key ANERDS-31:
    "epic link"= ANERDS-31
    or
    "epic link"= Jupiter

^ top of page

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).
Syntax
filter
Aliases
request , savedFilter , searchRequest
Field TypeFilter
Auto-complete

Yes

Supported operators

= , !=
IN , NOT IN

Unsupported operators~ , !~ , > , >= , < , <=
IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
Supported functions

None

Examples
  • Search the results of the filter "My Saved Filter" (which has an ID of 12000) for issues assigned to the user jsmith:
    filter ="My Saved Filter"and assignee = jsmith
    or
    filter =12000and assignee = jsmith

^ top of page

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.

Syntax
fixVersion
Field TypeVERSION
Auto-complete

Yes

Supported operators

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

Note that the comparison operators (e.g. ">") use theversion orderthat has
been set up by your project administrator, not a numeric or alphabetic order.

Unsupported operators~ , !~
Supported functions

When used with the=and!=operators, this field supports:

  • latestReleasedVersion()
  • earliestUnreleasedVersion()

When used with theINandNOT INoperators, this field supports:

  • releasedVersions()
  • unreleasedVersions()
Examples
  • Find issues with a Fix Version of 3.14 or 4.2:
    fixVersion in ("3.14","4.2")
    (Note that full-stops are reservedcharacters, so they need to be surrounded by quote-marks.)
  • Find issues with a Fix Version of "Little Ted":
    fixVersion ="Little Ted"
  • Find issues with a Fix Version ID of 10001:
    fixVersion =10001

^ top of page

Issue key

Search for issues with a particular issue key or issueID (i.e. the number that Jira automatically allocates to an issue).

Syntax
issueKey
Aliases
id , issue , key
Field TypeISSUE
Auto-complete

No

Supported operators

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

Unsupported operators~ , !~
IS, IS NOT, WAS NOT, WAS NOT IN, CHANGED
Supported functions

When used with theINorNOT INoperators,issueKeysupports:

  • issueHistory()
  • linkedIssues()
  • votedIssues()
  • watchedIssues()
Examples
  • Find the issue with key "ABC-123":
    issueKey = ABC-123

^ top of page

Issue link

Searches for issues linked or not linked to an issue. You can restrict the search to links of a particular type.

See Also
Document Management System Benefits, Features, and TipsBest document editing and management software of 2022Master Data Management – Why you’re doing it wrong and how to fix itInsurance Aggregators – The Best Way Forward for Insurance Agents

Syntax

issueLink, issueLink["link type"], or issueLinkType, where link type or LinkType is a variable you replace with the issue link type (blocks, duplicates, or is blocked by, for example).

Auto-complete

Yes

Supported operators

= , !=

IN , NOT IN

Unsupported operators

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

WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED , IS , IS NOT

Supported functions

None

Examples

Find issues:

  • with a link of any type to the issue ABC-123: issueLink = ABC-123
  • with linked issues but not linked to a specific issue: issueLink != ABC-123
  • linked to at least one of a list of issues: issueLink in (ABC-123, ABC-456)
  • with linked issues but not linked to any of the issues you specify: issueLink not in (ABC-123, ABC-456)
  • that block the issue ABC-123 (link type is "blocks"): issueBlocks = ABC-123 or issueLink["blocks"] = ABC-123
  • that are blocked by the issue ABC-123 (link type is "is blocked by"): issueIsBlockedBy = ABC-123 or issueLink["is blocked by"] = ABC-123

^ top of page

Issue link type

Search for issues that have a particular link type, likeblocksorisduplicated by.You can only find issues from the Jira instance you're searching on; remote links to issues on other Jira instances won’t be included.

Use this JQL query to add colors to your issue cards! For example, add a red stripe to issues that have some blockers, and keep all other issues green. This will help you bring the right information to your team’s attention, at a glance. For more info, see Customizing cards.

Syntax
issueLinkType
Auto-complete

Yes

Supported operators

= , !=
IN , NOT IN

Unsupported operators

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

WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED , IS , IS NOT

Supported functions

None

Examples

Find issues:

  • with a link type of "causes": issueLinkType = causes
  • with a link type of "duplicates" or "clones": issueLinkType in (duplicates,clones)
  • with link types other than “clones”: issueLinkType != clones
  • that are blocked by other issues, or that don't have any blockers:
    • issueLinkType = "is blocked by"
    • issueLinkType != "is blocked by"

Jira issue link types have the following properties:

  • Name: The title for the link type
  • Outward description: The description of how an issue affects other issues
  • Inward description: The description of how an issue is affected by other issues

For example, a link type could have the following properties:

  • Name: Problem/Incident
  • Outward description: causes
  • Inward description: is caused by

When searching issueLinkType, Jira searches all three properties. This can mean you're unable to isolate issues with a specific inward or outward description if the link type's name and either of the descriptions are the same. This is the case for the default "Blocks" link type, where the name and outward description are "blocks".

If you need to be able to search specifically for issues with an outward description of "blocks", for example, a Jira administrator must change the name of the link type to something else. If you're a Jira admin, take a look at Configuring issue linking for more info.

(Video) JQL Tutorial #4 - Smart Query Issues in Project by Reporter or Overdue

^ top of page

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 TypeLABEL
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 functionsNone
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 TypeDATE
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 theEQUALS,NOT EQUALS,GREATER THAN,GREATER THAN EQUALS,LESS THANorLESS THAN EQUALSoperators, 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"

^ top of page

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 securityname or issue level securityID (i.e. the number that Jira automatically allocates to an issue level security).

Note, it is safer to search by security levelID 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 TypeSECURITY 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)
  • Search for issues with a security level ID of 123:
    level =123

^ top of page

Organization

Used inJira Service Managementonly.

Search for all requests shared with an organization. Requests that were kept private won't be returned.

See Also
7 Best Free Appointment Scheduling Software for 2022Scrum Methodology Overview: Is It Right for Your Team?The best computer science careers in 2022The Best Hosted Endpoint Protection and Security Software for 2022

Syntax
organizations
Field TypeUSER
Auto-complete

Yes

Supported operators

= , !=

FAQs

What is advanced searching in Jira cloud? ›

The advanced search allows you to build structured queries using the Jira Query Language (JQL) to search for issues. You can specify criteria that you can't define in the quick or basic searches (the ORDER BY clause, for example). Created with Sketch. If you don't have complex search criteria, try quick search instead.

View Details ›
What does JQL consists of? ›

JQL stands for Jira Query Language and is the most powerful and flexible way to search for your issues in Jira. JQL is for everyone: developers, testers, agile project managers, and business users.

Tell Me More ›
Is JQL same as SQL? ›

Is JQL similar to SQL? JQL, like SQL and GraphQL, enables easy access to large data sets. These queries are similar in nature, even though they operate on different platforms. Jira Query Language enables anyone to build queries that can be executed in Jira to produce a set of results.

Get More Info Here ›
What are JQL fields? ›

JQL lets you search for a value in a specific field. Each field in Jira has a corresponding JQL name. If you've made a custom field, you'll be asked to name the field. In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions).

Continue Reading ›
What is the purpose of advanced search? ›

Using the advanced functions of Google, and/or specialised search engines, will get you more specific search results so you don't have to look through irrelevant results, and may find specifically relevant information that otherwise may not be available.

Explore More ›
What is Advanced Search used for? ›

Advanced search is a built-in feature of Google (and most search websites) that allows a user to specify additional requirements for a search. When used for searching the Web, an advanced search gives additional information to Google, which helps refine the search.

Learn More Now ›
How can I learn JQL? ›

Jira Basic Search - JQL 101 - YouTube

Know More ›
Why do we use JQL? ›

Jira Query Language (JQL) is a text-based search language for Jira. Using a human readable syntax, JQL provides users with an opportunity to utilize more complex operators and logic than what is available in basic search mode. This JQL statement is relatively straightforward to read and understand.

Get More Info Here ›
What are the three parts in a Jira workflow? ›

A Jira workflow has three basic components: statuses, transitions, and resolutions.

Get More Info Here ›
Can you do math with JQL? ›

JQL is a query language and does not support math operations.

Discover More ›

Which database is used by Jira? ›

Azure SQL is supported both for Jira Server and Jira Data Center.

Continue Reading ›
Why use Elasticsearch instead of SQL? ›

You plan to use Elasticsearch when you're doing a lot of text search, where traditional RDBMS databases are not performing really well (poor configuration, acts as a black-box, poor performance). Elasticsearch is highly customizable, extendable through plugins.

Show Me More ›
What are the different fields in Jira? ›

You can add the following types of custom fields to your request types, and make them visible on the customer portal:
  • Checkbox.
  • Date picker.
  • Date time picker.
  • Label.
  • Number field.
  • Radio Button.
  • Select List. Single choice. Multiple choice. Cascading.
  • Text field. Single-line. Multi-line.
13 Jul 2022

Read On ›
How do I create a JQL query? ›

Using JIRA's advanced search, JQL - YouTube

Know More ›
What are fields in Jira? ›

Jira application issues are made up of fields. You can choose any number of fields to appear when creating, editing, or transitioning issues. You can also create custom fields for teams working on issues within any of your Jira projects. Custom fields allow people to add information specific to your team's needs.

Read On ›
What are two types of advanced searches? ›

Advanced Search Techniques
  • What is Boolean Searching? Most searches will return too many or too few records. ...
  • Narrowing Searches. If your search returns too many records, you can narrow your search by adding more search terms. ...
  • Broadening Searches. ...
  • Proximity, Truncation and Wild Cards.

Learn More ›
When should you use the advanced search features? ›

Some useful features of advanced search:
  1. Site or domain search.
  2. Searching by country, language, time or region.
  3. Restrict the file type you search for (eg. PDF)
  4. Restrict the search by numbers, good for establishing number ranges such as date, price.
20 Nov 2020

Discover More ›
What are the benefits of using an advanced search in a database? ›

  • Sometimes a Basic Search is not specific enough - the database is just blindly matching keywords, after all. ...
  • An Advanced Search allows you to specify in which part of the article the database should look for your search terms. ...
  • You may not use many of these options.
19 Sept 2022

See More ›
How do I use advanced search operators? ›

Advanced operators are typically used to narrow searches and drill deeper into results. Search only in the page's title for a word or phrase. Use exact-match (quotes) for phrases. Search the page title for every individual term following "allintitle:".

See Details ›
How do I run advanced search? ›

Google Advanced Search
  1. Using the Google Advanced Search can help you find relevant materials for your studies using Google. ...
  2. Navigate to Google www.google.co.uk select (1) Settings and then select (2) Advanced Search.
  3. You are able to (1) enter your search terms. ...
  4. You will then see your search results.
20 Dec 2021

Read More ›

How do I get to advanced search on Google? ›

To access Advanced Search, enter a search and click the gear icon, like the one below, on the right side of the results page. If you plan on using Advanced Search often, you may want to bookmark the Google Advanced Search URL.

View More ›
How do I use advanced search in jira? ›

Query results can be saved and used as filters and views across Jira (including boards).
  1. In the top navigation bar, select Filters.
  2. Select Advanced issue search. ( ...
  3. Use quick filters for basic search or switch to JQL for advanced search.

Get More Info Here ›
What is the difference between search and advanced search? ›

In a Basic Search, you have just one search field. When performing a Basic Search, you need to connect keywords with Boolean operators (and, or, and not: click here for more information). In contrast, an Advanced Search has three search fields, with the option to add more.

Tell Me More ›
What is the difference between a quick search and an advanced search? ›

What is the difference between Quick Search and Advanced Search? Quick Search allows you to search a list based on a keyword such as a name or location that you type in. Advanced Search allows you to filter your lists by various criteria.

Keep Reading ›
What are the 2 common advanced web searching techniques? ›

Boolean Searching
  • What is Boolean Searching? Most searches will return too many or too few records. ...
  • Narrowing Searches. If your search returns too many records, you can narrow your search by adding more search terms. ...
  • Broadening Searches. ...
  • Proximity, Truncation and Wild Cards.

Tell Me More ›
What are the steps in using advanced search? ›

Do an Advanced Search
  1. On your computer, go to Advanced Search: google.com/advanced_search.
  2. Under “Find pages with,” choose the query field/s to: ...
  3. Enter the words that you want to include or remove from your results. ...
  4. Under "Then narrow your results by," choose the filters you want to use. ...
  5. Click Advanced Search.

Tell Me More ›
How can I learn JQL? ›

Jira Basic Search - JQL 101 - YouTube

Read More ›
How do you use advanced search techniques? ›

Advanced Search Techniques - YouTube

Discover More ›
What are the 5 basic information search techniques? ›

General search techniques that can be used in most databases and search engines are briefly described below.
  • Subject headings. In various databases, subject headings are assigned to publications. ...
  • Fillers. ...
  • Combining search terms. ...
  • AND. ...
  • Nesting terms. ...
  • Phrase searching. ...
  • Proximity operators (NEAR, NEXT, ADJ) ...
  • Truncating words.

Continue Reading ›
When should you use the advanced search features? ›

Some useful features of advanced search:
  1. Site or domain search.
  2. Searching by country, language, time or region.
  3. Restrict the file type you search for (eg. PDF)
  4. Restrict the search by numbers, good for establishing number ranges such as date, price.
20 Nov 2020

Know More ›

Does Google still have advanced search? ›

All you have to do is fill in the boxes on the page. In front of each box, you'll find an explanation of how that search will narrow down your results. Google's advanced search page can come in handy when you're looking for academic results, a specific type of image, or even an advanced video search.

Discover More Details ›
How many types of filters are available in Advanced Search? ›

When using Advanced Search there are 5 fields that allow you to run a search. There is no upper limit on filter criteria for list views. 1. Operators: drop-down displaying the Boolean operators used to narrow focus of the search.

Keep Reading ›
What are the types of search techniques? ›

Effective Search Techniques
  • Keyword Searching. Use a keyword search to search all parts of a source for the words you enter in the search box. ...
  • Boolean Searching. ...
  • Subject Searching. ...
  • Limiters. ...
  • Phrase Searching. ...
  • Using References/Works Cited Lists.

Read On ›
What is the most advanced search engine? ›

  1. Google. Besides being the most popular search engine covering over 90% of the worldwide market, Google boasts outstanding features that make it the best search engine in the market. ...
  2. Bing. ...
  3. 3. Yahoo. ...
  4. Baidu. ...
  5. Yandex. ...
  6. Duckduckgo. ...
  7. Contextual Web Search. ...
  8. Yippy Search.
24 Jan 2022

Continue Reading ›
What are the 4 search strategies? ›

Searching for exact phrases. Using truncated and wildcard searches. Searching with subject headings. Using Boolean logic.
...
Use Boolean logic to combine search terms
  • OR.
  • AND.
  • NOT.

Continue Reading ›
What is searching any 3 types of searching? ›

Types of searches: transactional, navigational, informational.

Keep Reading ›
What are the three main types of searching? ›

It is commonly accepted that there are three different types of search queries: Navigational search queries. Informational search queries. Transactional search queries.

Read The Full Story ›

Videos

1. 1 Hour to Master JQL Basics | Crash Course
(Apetech Tech Tutorials)
2. Mastering JQL in Jira Cloud
(idalkoTools)
3. Complex Queries in JQL - JQL 101
(Atlassian)
4. JQL Tutorial #13 - JQL Operators Tutorial | Contains and Not Contains
(RCV Academy)
5. (#23) JQL(Jira Query Language) in Jira | Advanced Search in Jira | JIRA Tutorial
(WebGentle)
6. JQL Tutorial #9 - How Does JQL Work | JQL Query Basics
(RCV Academy)
Top Articles
Latest Posts
Article information

Author: Duncan Muller

Last Updated: 15/03/2023

Views: 5723

Rating: 4.9 / 5 (79 voted)

Reviews: 86% of readers found this page helpful

Author information

Name: Duncan Muller

Birthday: 1997-01-13

Address: Apt. 505 914 Phillip Crossroad, O'Konborough, NV 62411

Phone: +8555305800947

Job: Construction Agent

Hobby: Shopping, Table tennis, Snowboarding, Rafting, Motor sports, Homebrewing, Taxidermy

Introduction: My name is Duncan Muller, I am a enchanting, good, gentle, modern, tasty, nice, elegant person who loves writing and wants to share my knowledge and understanding with you.