Advanced Searching - Fields Reference

A field in JQL is a word that represents a JIRA field (or a custom field that has already been defined in JIRA). 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.

List of Fields:

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

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 which rely on that name. Version IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
affectedVersion
Field Type

VERSION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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.

Supported Functions
When used with the IN and NOT IN operators, this field supports:
  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
Examples
  • Find issues with an AffectedVersion of 3.14:

    affectedVersion = "3.14"

    (Note that full-stops are reserved characters, so they 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 fields | ^^top of topic

Assignee

Search for issues that are assigned to a particular user. You can search by the user's Full Name, ID or Email Address.

Note: this field supports auto-complete.

Syntax
assignee
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
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 "John Smith"

    or

     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, so the email address needs to be surrounded by quote-marks.)

^top of fields | ^^top of topic

Attachments

Search for issues which have or do not have attachments. You can only use the EMPTY or IS NOT EMPTY operators for this field.

Note: this field supports auto-complete.

Syntax
attachments
Field Type

ATTACHMENT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

None

Examples
  • Search for issues which have attachments

    attachments IS NOT EMPTY
  • Search for issues which do not have attachments

    attachments IS EMPTY

^top of fields | ^^top of topic

Category

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

Note: this field supports auto-complete.

Syntax
category
Field Type

CATEGORY

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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

     category = "Alphabet Projects"

^top of fields | ^^top of topic

Comment

Search for issues that have a Comment which contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
comment
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where a Comment contains text that matches "My PC is quite old" (i.e. a "fuzzy" match:

    comment ~ "My PC is quite old"
  • Find issues where a Comment contains the exact phrase "My PC is quite old":

    comment ~ "\"My PC is quite old\""

^top of fields | ^^top of topic

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

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 which rely on that name. Component IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
component
Field Type

COMPONENT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

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

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 fields | ^^top of topic

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

Note: this field does not support auto-complete.

Syntax
created

Alias:

createdDate
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 midnight 00:00 12th December 2010:

    created < "2010/12/12"
  • Find all issues created on or before 12th December 2010 (but not 13th 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 fields | ^^top of topic

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: this field supports auto-complete.

Syntax
creator
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

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 "bob@mycompany.com":

    creator = "bob@mycompany.com"

    (Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

^top of fields | ^^top of topic

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

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 on 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 which rely on that name. Custom Field IDs, however, are unique and cannot be changed.

Note:

  • JIRA text-search syntax can be used with Custom Fields of type 'Text'.
  • auto-complete is supported for Custom Fields of type picker, group picker, select, check-box and radio button fields.
Syntax
CustomFieldName

Alias:

cf[CustomFieldID]
Field Type

Depends on the Custom Field's configuration

Supported Operators

Different types of Custom Fields support different operators. For the default Custom Field Types, the following operators are supported:

  • Number and date/time fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (tick)

    (tick)

    (error)

    (error)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)
  • Picker, select, check-box and radio button fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)

    (tick)

    (tick)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)
  • Text fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (error)

    (error)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)
Supported Functions

Different types of Custom Fields support different functions. For the default Custom Field Types, the following functions are supported:

  • Date/time fields:
    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()
  • 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

^top of fields | ^^top of topic

Description

Search for issues where the Description contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
description
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Description contains text that matches "Please see screenshot" (i.e. a "fuzzy" match):

    description ~ "Please see screenshot"
  • Find issues where the Description contains the exact phrase "Please see screenshot":

    description ~ "\"Please see screenshot\""

^top of fields | ^^top of topic

Due

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

Note: this field does not support auto-complete.

Syntax
due

Alias:

dueDate
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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"

^top of fields | ^^top of topic

Environment

Search for issues where the Environment contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
environment
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Environment contains text that matches "Third floor" (i.e. a "fuzzy" match):

    environment ~ "Third floor"
  • Find issues where the Environment contains the exact phrase "Third floor":

    environment ~ "\"Third floor\""

^top of fields | ^^top of topic

(info) Only available if you are using JIRA Agile 6.1.2 or later.

Search for issues that belong to a particular Epic in JIRA Agile. 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).

Note: this field does not support auto-complete.

Syntax
"epic link"
Field Type

Epic Link Relationship (this is a custom type created by JIRA Agile).

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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", which has issue key ANERDS-317:

    "epic link" = ANERDS-317

    or

    "epic link" = Jupiter

^top of fields | ^^top of topic

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

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.

Note:

  • An Advanced Searching - Fields Reference 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).
  • This field supports auto-complete.
    Syntax
    filter

    Aliases:

    request
    savedFilter
    searchRequest
Field Type

FILTER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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

^top of fields | ^^top of topic

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

Note: this field supports auto-complete.

Syntax
fixVersion
Field Type

VERSION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

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.

Supported Functions
When used with the IN and NOT IN operators, this field supports:
  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
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

^top of fields | ^^top of topic

Issue Key

Search for issues with a particular Issue Key or Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support auto-complete.

Syntax
issueKey

Aliases:

id
issue
key
Field Type

ISSUE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 

^top of fields | ^^top of topic

LastViewed

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

Note: this field does not support auto-complete.

Syntax
lastViewed
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

Supported Functions

When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()

Examples
  • Find all issues last viewed before 12th December 2010:

    lastViewed < "2010/12/12"
  • Find all issues last viewed on or before 12th December 2010 (but not 13th 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 fields | ^^top of topic

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 Security Level name or Issue Security Level ID (i.e. the number that JIRA automatically allocates to an Issue Security Level).

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 which rely on that name. Security Level IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
level
Field Type

SECURITY LEVEL

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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 fields | ^^top of topic

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.

Note: this field does not support auto-complete.

Syntax
originalEstimate

Alias:

timeOriginalEstimate
Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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

^top of fields | ^^top of topic

Parent

Only available if sub-tasks have been enabled by your JIRA administrator.

Search for all sub-tasks of a particular issue. You can search by Issue Key or by Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support auto-complete.

Syntax
parent
Field Type

ISSUE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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

    parent = TEST-1234

^top of fields | ^^top of topic

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

It is safer to search by Priorty 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 which rely on that name. Priority IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
priority
Field Type

PRIORITY

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

Examples
  • Find issues with a Priority of "High":

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

    priority = 10000

^top of fields | ^^top of topic

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.

Note: this field supports auto-complete.

Syntax
project
Field Type

PROJECT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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

^top of fields | ^^top of topic

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.

Note: this field does not support auto-complete.

Syntax
remainingEstimate

Alias:

timeEstimate
Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues with a Remaining Estimate of more than 4 hours:

     remainingEstimate > 4h 

^top of fields | ^^top of topic

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.

Note: this field supports auto-complete.

Syntax
reporter
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
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"

    or

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

^top of fields | ^^top of topic

Resolution

Search for issues that have a particular Resolution

You can search by Resolution name or Resolution ID (i.e. the number that JIRA automatically allocates to a Resolution).

It is safer to search by Resolution ID than Resolution name

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

Note: this field supports auto-complete.

Syntax
resolution
Field Type

RESOLUTION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

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

^top of fields | ^^top of topic

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

Note: this field does not support auto-complete.

Syntax
resolved

Alias:

resolutionDate
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 (but not on 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

^top of fields | ^^top of topic

Sprint

(info) Only available if you are using JIRA Agile.

Search for issues that are assigned to a particular sprint in JIRA Agile. 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).

Syntax
sprint

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

Field Type

Number

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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

^top of fields | ^^top of topic

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 is safer to search by Status ID than Status name

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

Please note, though, that the WAS, WAS_NOT, WAS_IN and WAS_NOT_IN operators can only be used with the name (not the ID).

Note: this field supports auto-complete.

Syntax
status
Field Type

STATUS

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

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

^top of fields | ^^top of topic

Summary

Search for issues where the Summary contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
summary
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Summary contains text that matches "Error saving file" (i.e. a "fuzzy" match):

    summary ~ "Error saving file"
  • Find issues where the Summary contains the exact phrase "Error saving file":

    summary ~ "\"Error saving file\""

^top of fields | ^^top of topic

Text

This is a "master-field" that allows you to search all text fields, i.e.:

The JQL field "text" as in text ~ "some words" searches an issue's Summary, Description, Environment, Comments. It also searches all text custom fields. If you have many text custom fields you can improve performance of your queries by searching on specific fields, e.g.
Summary ~ "some words" OR Description ~ "some words"

Notes:

Syntax
text
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where a text field matches the word "Fred":

    text ~ "Fred"

    or

    text ~ Fred
  • Find all issues where a text field contains the exact phrase "full screen":

    text ~ "\"full screen\""

^top of fields | ^^top of topic

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

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 which rely on that name. Type IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
type

Alias:

issueType
Field Type

ISSUE_TYPE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues with an Issue Type of "Bug":

    type = Bug
  • Find issues with an Issue Type of "Bug" or "Improvement":

     issueType in (Bug,Improvement)
  • Find issues with an Issue Type ID of 2:

    issueType = 2

^top of fields | ^^top of topic

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.

Note: this field does not support auto-complete.

Syntax
timeSpent
Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Time Spent is more than 5 days:

    timeSpent > 5d

^top of fields | ^^top of topic

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

Note: this field does not support auto-complete.

Syntax
updated

Alias:

updatedDate
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 (but not 13th 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"

^top of fields | ^^top of topic

Voter

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

Note: this field supports auto-complete.

Syntax
voter
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 for which you have voted:

    voter = currentUser()
  • Search for issues for which the user "jsmith" has voted:

    voter = "jsmith"
  • Search for issues for which a member of the group "jira-developers" has voted:

    voter in membersOf("jira-developers")

^top of fields | ^^top of topic

Votes

Search for issues with a specified number of votes.

Note: this field does not support auto-complete.

Syntax
votes
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find all issues that have 12 or more votes:

    votes >= 12

^top of fields | ^^top of topic

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.

Note: this field supports auto-complete.

Syntax
watcher
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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-developers":

    watcher in membersOf("jira-developers")

^top of fields | ^^top of topic

Watchers

Search for issues with a specified number of watchers.

Note: this field does not support auto-complete.

Syntax
watchers
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

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

    watchers > 3

^top of fields | ^^top of topic

Work Log Author

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

Search for issues a particular user has logged work against. You can search by the user's Full Name, ID, or Email Address. Note that you can only find issues for which you have "Time Tracking" permissions, unless you are searching for issues that you've logged work against.

Note: this field supports auto-complete.

Syntax
worklogAuthor
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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've logged work against:

    worklogAuthor = currentUser()
  • Search for issues that the user "jsmith" has logged work against:

    worklogAuthor = "jsmith"
  • Search for issues that a member of the group "jira-developers" has logged work against:

    worklogAuthor in membersOf("jira-developers")

^top of fields | ^^top of topic

Work Log Comment

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

Search for issues that have a Comment in a work log entry which contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
worklogComment
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

Supported Functions

n/a

Examples
  • Find issues where a Comment in a work log entry contains text that matches "test sessions" (i.e. a "fuzzy" match):

    comment ~ "test sessions"
  • Find issues where a Comment contains the exact phrase "test sessions":

    comment ~ "\"test sessions\""

^top of fields | ^^top of topic

Work Log Date

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

Search for issues that have comments in work log entries that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight 00:00 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).

Note: this field does not support auto-complete.

Syntax
worklogDate
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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 have comments in work log entries created before midnight 00:00 12th December 2010:

    worklogDate < "2010/12/12"
  • Find issues that have comments in work log entries created on or before 12th December 2010 (but not 13th December 2010):

    worklogDate <= "2010/12/13"
  • Find issues that have comments in work log entries created on 12th December 2010 before 2:00pm:

    worklogDate > "2010/12/12" and worklogDate < "2010/12/12 14:00"
  • Find issues that have comments in work log entries created less than one day ago:

    worklogDate > "-1d"
  • Find issues that have comments in work log entries created in January 2011:

    worklogDate > "2011/01/01" worklogDate < "2011/02/01"
  • Find issues that have comments in work log entries created on 15 January 2011:

    worklogDate > "2011/01/15" and worklogDate < "2011/01/16"

^top of fields | ^^top of topic

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

Note: this field does not support auto-complete.

Syntax
workRatio
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues on which more than 75% of the Original Estimate has been spent:

     workRatio > 75

^top of fields | ^^top of topic

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport