• Products
  • Documentation
  • Resources

Jira Automation docs have moved

All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs.

Go to Cloud Automation documentation | Why did we do this?

Advanced search reference - 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). 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. It's 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

1 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 = and != operators, this field supports:

  • latestReleasedVersion()

  • earliestUnreleasedVersion()

When used with the IN and NOT IN operators, 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

Approvals

Used in Jira Service Management only.

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

Syntax

1 approvals

Field Type

USER

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:
    approval = approver(jsmith)

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

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

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

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

1 assignee

Field Type

USER

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

  • 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.

Attachments

Search for issues that have or do not have attachments. 

Syntax

1 attachments

Field Type

ATTACHMENT

Auto-complete

Yes

Supported operators

IS, IS NOT

Unsupported operators

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

Supported functions

None

Examples

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

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

Category

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

Syntax

1 category

Field Type

CATEGORY

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 that belong to projects in the "Alphabet Projects" Category:
    category = "Alphabet Projects"

Change gating type

Used in Jira Service Management only.

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

1 change-gating-type

Field Type

TEXT

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"

Comment

Search for issues that have a comment that contains particular text using Jira text-search syntax. Learn more about searching syntax for text fields.

Syntax

1 comment

Field Type

TEXT

Auto-complete

No

Supported operators

~ , !~

Unsupported operators

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

Supported functions

None

Examples

  • Find issues where a comment contains the words "My PC is quite old":
    comment ~ "\"My PC is quite old"

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

1 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)
    or
    component = Comp1 and component = Comp2 

  • Find issues in the component with ID 20500:
    component = 20500 

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

1 created

Alias

1 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. Note that an issue's creator does not change, so you cannot search for past creators (e.g. WAS). See Reporter for more options. 

Syntax

1 creator

Field Type

USER

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 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"
    or
    creator = "jjones"

  • Search for issues that were created by the user with email address :
    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.

Syntax

1 CustomFieldName

Alias

1 cf[CustomFieldID]

Field Type

Depends on the custom field's configuration

Jira text-search syntax can be used with custom fields of type 'Text'. Learn more about searching syntax for text fields.

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 different operators.

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 different functions.

Supported functions:
date/time fields 

When used with the EQUALSNOT EQUALSGREATER THANGREATER THAN EQUALS
LESS THAN or LESS THAN EQUALS operators, 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 the IN and NOT IN operators, 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

Customer Request Type

Used in Jira Service Management only.

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

1 "Customer Request Type"

Field Type

Custom field

Auto-complete

Yes

Supported operators

1 = , !=

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, is portal-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")

Description

Search for issues where the description contains particular text using Jira text-search syntax. Learn more about searching syntax for text fields.

Syntax

1 description

Field Type

TEXT

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"

Due

Search for issues that were due on, before, or after a particular date (or date range). Note that the due date relates to the date only (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

1 due

Alias

1 dueDate

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

Environment

Search for issues where the environment contains particular text using Jira text-search syntax. Learn more about searching syntax for text fields.

Syntax

1 environment

Field Type

TEXT

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"

Search for issues that belong to a particular epic in company-managed projects. 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.

Syntax

1 "epic link"

Field Type

Epic 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 the IN or NOT IN operators, epic link supports:

  • 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

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

1 filter

Aliases

1 request , savedFilter , searchRequest

Field Type

Filter

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 = 12000 and assignee = jsmith

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).

It’s 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

1 fixVersion

Field Type

VERSION

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 functions

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

  • latestReleasedVersion()

  • earliestUnreleasedVersion()

When used with the IN and NOT IN operators, 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 reserved characters, 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

Hierarchy level

This feature is rolling out to customers. You might not see it on your site just yet.

Filter issues according to their hierarchy level using a JQL filter. This field uses numbers that correlate to hierarchy levels. Use:

  • 1 to filter by parent level task, such as epics. This level is defined by your Jira administrator.

  • 0 to filter by standard level issues, such as stories or tasks

  • -1 to filter by subtasks

Currently, this field doesn’t support custom hierarchy levels made in Advanced Roadmaps.

Syntax

1 hierarchyLevel

Field Type

Number

Auto-complete

Yes

Supported operators

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

Unsupported operators

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

Supported functions

  • None

Examples

  • Find issues at the story level: hierarchyLevel = "0"

  • Find issues higher than the subtask level: hierarchyLevel > -1

Issue key

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

Syntax

1 issueKey

Aliases

1 id , issue , key

Field Type

ISSUE

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported functions

When used with the IN or NOT IN operators, issueKey supports:

  • issueHistory()

  • linkedIssues()

  • votedIssues()

  • watchedIssues()

Examples

  • Find the issue with key "ABC-123":
    issueKey = ABC-123

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

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

Search for issues that have a particular link type, like blocks or is duplicated 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

1 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.

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

1 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

1 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 EQUALSNOT EQUALSGREATER THANGREATER THAN EQUALSLESS 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

1 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)

  • Search for issues with a security level ID of 123:
    level = 123

Organization

Used in Jira Service Management only.

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

Syntax

1 organizations

Field Type

USER

Auto-complete

Yes

Supported operators

= , !=
IN, NOT IN

Examples

Search for all requests shared with the organization Atlassian:

1 organizations = "Atlassian"

Original estimate

Only available if time-tracking has been enabled by your Jira administrator.

Search for issues where the original estimate is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.

Syntax

1 originalEstimate

Alias

1 timeOriginalEstimate

Field Type

DURATION

Auto-complete

No

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 original estimate of 1 hour:
    originalEstimate = 1h

  • Find issues with an original estimate of more than 2 days:
    originalEstimate > 2d

Parent

Search for all subtasks of a particular issue in company-managed projects or subtasks of a particular epic in team-managed projects. You can search by issue key or by issue ID (i.e. the number that Jira automatically allocates to an Issue).

Syntax

1 parent

Field Type

ISSUE

Auto-complete

No

Supported operators

= , !=
IN , NOT IN

Unsupported operators

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

Supported functions

None

Examples

  • Find issues that are sub-tasks of issue TEST-1234:
    parent = TEST-1234

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

1 priority

Field Type

PRIORITY

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 priority of "High":
    priority = High

  • Find issues with a priority ID of 10000:
    priority = 10000

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

1 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

Project type

Search for issues that belong to a particular type of project, either:

  • “business” which finds issues created in Jira Work Management projects

  • “software” which finds issues created in Jira Software projects

  • “service_desk” which finds issues created in Jira Service Management projects

Results depend on your permission level. You will only see results for products you have access to. Learn more about product access.

Syntax

projectType

Auto-complete

Yes

Supported operators

=, !=

IN, NOT IN

Unsupported operators

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

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

Supported functions

None

Examples

Find all issues in a software project:

projectType = ”software”

Find all issues in either a software project or a service project:

projectType = ”software” OR projectType = ”service_desk”

Find all issues that aren’t in a software project:

projectType != ”software”

Remaining estimate

Only available if time-tracking has been enabled by your Jira administrator.

Search for issues where the remaining estimate is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.

Syntax

1 remainingEstimate

Alias

1 timeEstimate

Field Type

DURATION

Auto-complete

No

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 a remaining estimate of more than 4 hours:
    remainingEstimate > 4h

Reporter

Search for issues that were reported by a particular user. This may be the same as the creator, but can be distinct. You can search by the user's full name, ID, or email address.

Syntax

1 reporter

Field Type

USER

Auto-complete

Yes

Supported operators

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

Unsupported operators

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

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 reported by Jill Jones:
    reporter = "Jill Jones"orreporter = jjones

  • 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.)

Request channel type

Used in Jira Service Management only.

Search for requests by the channel that they were created by. For example, you could search for all requests that were emailed to the service project, or all requests that were sent from a customer portal.

Syntax

1 request-channel-type

Field Type

TEXT

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:

  • email: requests sent by email

  • jira: issues created in Jira (by clicking the blue Create button)

  • portal: requests sent from a service project portal

  • anonymous portal: requests sent from the customer portal by a customer who was not logged in

  • api: requests sent by REST API

Examples

  • Find requests where the request channel was email:
    request-channel-type = email

  • Find requests where the request channel was something other than a service project portal:
    request-channel-type != portal

  • Find requests where the request channel was sent by a CI/CD deployment tool:
    request-channel-type = deployment

Request last activity time

Used in Jira Service Management only.

Search for requests 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. Search results are 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

1 request-last-activity-time

Field Type

DATE

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 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 acted on before 23rd May 2016:
    request-last-activity-time < "2016/05/23"

    • Find all issues last acted on or before 23rd May 2016:
      request-last-activity-time <= "2016/05/23"

    • Find all issues created on 23rd May 2016 and last acted on before 2:00pm that day:
      created > "2016/05/23" AND request-last-activity-time < "2016/05/23 14:00" 

    • Find issues last acted on less than one day ago:
      request-last-activity-time > "-1d"

    • Find issues last acted on in January 2016:
      request-last-activity-time > "2016/01/01" and request-last-activity-time < "2016/02/01"

Resolution

The resolution field doesn't exist in Jira Service Management team-managed projects. This means you can't search for issues in Jira Service Management team-managed projects with the resolution field. Instead, you can use the statusCategory field (an issue is resolved when statusCategory = Done).

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

1 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")

  • Find issues with a resolution ID of 5:
    resolution = 5

  • Find issues that do not have a resolution:
    resolution = unresolved

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

1 resolved

Alias

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

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

  • Find issues that were resolved in the last hour:
    resolved > -1h

SLA

Used in Jira Service Management only.

Search and sort through your requests to ensure that you're hitting your SLA goals. You can search for requests whose SLAs are in a certain state of completion, or that have a certain amount of time on their SLA clock. 

Syntax

1 Time to resolution

Time to first response

<your custom SLA name>

Field Type

SLA

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported functions

  • breached()

  • completed()

  • elapsed()

  • everBreached()

  • paused()

  • remaining()

  • running()

  • withinCalendarHours()

Examples

  • Find issues where Time to First Response was breached:
    "Time to First Response" = everBreached()

  • Find issues where the SLA for Time to Resolution is paused due to a condition:
    "Time to Resolution" = paused()

  • Find issues where the SLA for Time to Resolution is paused due to the SLA calendar:
    "Time to Resolution" = withinCalendarHours()

  • Find issues that have been waiting for a response for more than 1 hour:
    "Time to First Response" > elapsed("1h")

  • Find issues that that will breach Time to First Response in the next two hours:
    "Time to First Response" < remaining("2h")

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).

Syntax

1 sprint

Field Type

NUMBER

Auto-complete

Yes

Supported operators

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

Unsupported operators

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

Supported functions

  • openSprints()

  • closedSprints()

Examples

  • Find issues that belong to sprint 999:
    sprint = 999

  • Find issues that belong to sprint "February 1":
    sprint = "February 1"

  • Find issues that belong to either "February 1", "February 2" or "February 3":
    sprint in ("February 1","February 2","February 3")

  • Find issues that are assigned to a sprint:
    sprint is not empty

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).

It’s safer to search by status ID than status name since it’s possible for your Jira administrator to change the name of a status, which would break any saved filter that relies 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

1 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

Summary

Search for issues where the summary contains specific text using Jira text-search syntax. Learn more about searching syntax for text fields.

Syntax

1 summary

Field Type

TEXT

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 summary contains the words "Error saving file":
    summary ~ "Error saving file"

Text

This is a master-field that allows you to search all text fields for issues, such as:

  • Summary

  • Description

  • Environment

  • Comments

  • custom fields that use the "free text searcher"; this includes custom fields of the following built-in custom field types:

    • Free text field (unlimited text)

    • Text field (< 255 characters)

    • Read-only text field

Search for issues that have certain text present using Jira text-search syntax. Learn more about searching syntax for text fields.

The text master-field can only be used with the CONTAINS operator ("~").

Syntax

1 text

Field Type

TEXT

Auto-complete

No

Supported operators

~

Unsupported operators

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

Supported functions

None

Examples

  • Find issues where a text field contains the word "Fred":
    text ~ "Fred"
    or
    text ~ Fred

  • Find all issues where a text field contains the words "full screen":
    text ~ "full screen"

Time spent

Only available if time-tracking has been enabled by your Jira administrator.

Search for issues where the time spent is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.

Syntax

1 timeSpent

Field Type

DURATION

Auto-complete

No

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 where the time spent is more than 5 days:
    timeSpent > 5d

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

1 type

Alias

1 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)

  • Find issues with an issue type ID of 2:
    issueType = 2

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

1 updated

Alias

1 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. 

Syntax

1 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")

Votes

Search for issues with a specified number of votes.

Syntax

1 votes

Field Type

NUMBER

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported functions

None

Examples

  • Find all issues that have 12 or more votes:
    votes >= 12

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.

Syntax

1 watcher

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 are watching:
    watcher = currentUser()

  • Search for issues that the user "jsmith" is watching:
    watcher = "jsmith"

  • Search for issues that are being watched by a member of the group "jira-administrators":
    watcher in membersOf("jira-administrators")

Watchers

Search for issues with a specified number of watchers.

Syntax

1 watchers

Field Type

NUMBER

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported functions

None

Examples

  • Find all issues that are being watched by more than 3 people:
    watchers > 3

Worklog comment

This field is only available if time tracking has been enabled by your Jira administrator, and can only support the CONTAINS operator ("~").

Search for issues that have certain text present in worklog comments using Jira text-search syntax. Learn more about searching syntax for text fields.

Syntax

1 worklogComment

Field Type

TEXT

Auto-complete

No

Supported operators

~

Unsupported operators

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

Supported functions

None

Examples

  • Find issues where a worklog comment contains the word "Fred":
    worklogComment ~ "Fred"

  • Find all issues where a worklog comment contains the words "full screen":
    worklogComment ~ "full screen"

Worklog date

Only available if time-tracking has been enabled by your Jira administrator.

Search for issues with work logged on a specific date

Syntax

1 worklogDate

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 where someone logged work on 12th December 2010:
    worklogDate = "2010/12/12"

  • Find the issues where someone has logged work in the past week:
    worklogDate > startOfWeek()

Work ratio

Only available if time-tracking has been enabled by your Jira administrator.

Search for issues where the work ratio has a particular value. Work ratio is calculated as follows: workRatio = timeSpent / originalEstimate) x 100

Syntax

1 workRatio

Field Type

NUMBER

Auto-complete

No

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 on which more than 75% of the original estimate has been spent:
    workRatio > 75

 

Additional Help