Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Content Zone
maxLevel4
locationtop
minLevel4
typelist

Anchor
affectedVersion
affectedVersion
Anchor
AffectedVersion
AffectedVersion

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

Info
titleIt 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
Code Block
affectedVersion
Field Type

VERSION

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields

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
Include Page
__JQL Functions supported by Version Fields
nopaneltrue
__JQL Functions supported by Version Fields
Examples
  • Find issues with an AffectedVersion of 3.14:

    Code Block
    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":

    Code Block
    affectedVersion = "Big Ted"
  • Find issues with an AffectedVersion ID of 10350:

    Code Block
    affectedVersion = 10350

^top of fields | ^^top of topic

Anchor
Assignee
Assignee

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
Code Block
assignee
Field Type

USER

Supported Operators
Include Page
__JQLOpSBSelectFields(inWASCHANGED)
nopaneltrue
__JQLOpSBSelectFields(inWASCHANGED)
Supported Functions
Include Page
__JQL Functions supported by User Fields
nopaneltrue
__JQL Functions supported by User Fields
Examples
  • Find issues that are assigned to John Smith:

    Code Block
    assignee = "John Smith"

    or

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

    Code Block
     assignee WAS "John Smith"

    or

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

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

Anchor
Category
Category

Category

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

Note: this field supports auto-complete.

Syntax
Code Block
category
Field Type

CATEGORY

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions

n/a

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

    Code Block
     category = "Alphabet Projects"

^top of fields | ^^top of topic

Anchor
Comment
Comment
Anchor
Comments
Comments

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
Code Block
comment
Field Type

TEXT

Supported Operators
Include Page
__JQLOpSBTextFields(exIS)
nopaneltrue
__JQLOpSBTextFields(exIS)
Supported Functions

n/a

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

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

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

^top of fields | ^^top of topic

Anchor
Component
Component

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

Info
titleIt 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
Code Block
component
Field Type

COMPONENT

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions

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

Examples
  • Find issues in the "Comp1" or "Comp2" component:

    Code Block
     component in (Comp1, Comp2)
  • Find issues in the "Comp1" and"Comp2" components:

    Code Block
     component in (Comp1) and component in (Comp2)

    or

    Code Block
     component = Comp1 and component = Comp2
  • Find issues in the component with ID 20500:

    Code Block
    component = 20500

^top of fields | ^^top of topic

Anchor
Created
Created
Anchor
CreatedDate
CreatedDate
Anchor
createdDate
createdDate

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

Include Page
__JQL Date Time Formats
nopaneltrue
__JQL Date Time Formats

Note: this field does not support auto-complete.

Syntax
Code Block
created

Alias:

Code Block
createdDate
Field Type

DATE

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions
Include Page
__JQL Functions supported by Date Fields
nopaneltrue
__JQL Functions supported by Date Fields
Examples
  • Find all issues created before 12th December 2010:

    Code Block
    created < "2010/12/12"
  • Find all issues created on or before 12th December 2010:

    Code Block
    created <= "2010/12/13"
  • Find all issues created on 12th December 2010 before 2:00pm:

    Code Block
    created > "2010/12/12" and created < "2010/12/12 14:00"
  • Find issues created less than one day ago:

    Code Block
    created > "-1d"
  • Find issues created in January 2011:

    Code Block
    created > "2011/01/01" and created < "2011/02/01"
  • Find issues created on 15 January 2011:

    Code Block
    created > "2011/01/15" and created < "2011/01/16"

^top of fields | ^^top of topic

Anchor
custom
custom

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

Info
titleIt 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 (except 'Cascading Select'), check-box and radio button fields.
Syntax
Code Block
CustomFieldName

Alias:

Code Block
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:
    Include Page
    __JQLOpSBNumericFields
    nopaneltrue
    __JQLOpSBNumericFields
  • Picker, select, check-box and radio button fields:
    Include Page
    __JQLOpSBSelectFields
    nopaneltrue
    __JQLOpSBSelectFields
  • Text fields:
    Include Page
    __JQLOpSBTextFields
    nopaneltrue
    __JQLOpSBTextFields
Supported Functions

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

  • Date/time fields:
    Include Page
    __JQL Functions supported by Date Fields
    nopaneltrue
    __JQL Functions supported by Date Fields
  • Version picker fields:
    Include Page
    __JQL Functions supported by Version Fields
    nopaneltrue
    __JQL Functions supported by Version Fields
Examples
  • Find issues where the value of the "Location" Custom Field is "New York":

    Code Block
    location = "New York"
  • Find issues where the value of the Custom Field with ID 10003 is "New York":

    Code Block
    cf[10003] = "New York"
  • Find issues where the value of the "Location" Custom Field is "London" or "Milan" or "Paris":

    Code Block
    cf[10003] in ("London", "Milan", "Paris")
  • Find issues where the "Location" Custom Field has no value:

    Code Block
    location != empty

^top of fields | ^^top of topic

Anchor
Description
Description

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
Code Block
description
Field Type

TEXT

Supported Operators
Include Page
__JQLOpSBTextFields
nopaneltrue
__JQLOpSBTextFields
Supported Functions

n/a

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

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

    Code Block
    description ~ "\"Please see screenshot\""

^top of fields | ^^top of topic

Anchor
Due
Due
Anchor
DueDate
DueDate
Anchor
dueDate
dueDate

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

Include Page
__JQL Date Formats
nopaneltrue
__JQL Date Formats

Note: this field does not support auto-complete.

Syntax
Code Block
due

Alias:

Code Block
dueDate
Field Type

DATE

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions
Include Page
__JQL Functions supported by Date Fields
nopaneltrue
__JQL Functions supported by Date Fields
Examples
  • Find all issues due before 31st December 2010:

    Code Block
    due < "2010/12/31"
  • Find all issues due on or before 31st December 2010:

    Code Block
    due <= "2011/01/01"
  • Find all issues due tomorrow:

    Code Block
    due = "1d"
  • Find all issues due in January 2011:

    Code Block
    due >= "2011/01/01" and due <= "2011/01/31"
  • Find all issues due on 15 January 2011:

    Code Block
    due = "2011/01/15"

^top of fields | ^^top of topic

Anchor
Environment
Environment

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
Code Block
environment
Field Type

TEXT

Supported Operators
Include Page
__JQLOpSBTextFields
nopaneltrue
__JQLOpSBTextFields
Supported Functions

n/a

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

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

    Code Block
    environment ~ "\"Third floor\""

^top of fields | ^^top of topic

Anchor
filter
filter

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

Info
titleIt 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 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
    Code Block
    filter

    Aliases:

    Code Block
    request
    Code Block
    savedFilter
    Code Block
    searchRequest
Field Type

FILTER

Supported Operators
Include Page
__JQLOpSBSelectFields(exIS)
nopaneltrue
__JQLOpSBSelectFields(exIS)
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:

    Code Block
    filter = "My Saved Filter" and assignee = jsmith

    or

    Code Block
    filter = 12000 and assignee = jsmith

^top of fields | ^^top of topic

Anchor
FixVersion
FixVersion
Anchor
fixVersion
fixVersion

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

Info
titleIt 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
Code Block
fixVersion
Field Type

VERSION

Supported Operators
Include Page
__JQLOpSBNumericFields(inWASCHANGED)
nopaneltrue
__JQLOpSBNumericFields(inWASCHANGED)

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
Include Page
__JQL Functions supported by Version Fields
nopaneltrue
__JQL Functions supported by Version Fields
Examples
  • Find issues with a Fix Version of 3.14 or 4.2:

    Code Block
     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":

    Code Block
    fixVersion = "Little Ted"
  • Find issues with a Fix Version ID of 10001:

    Code Block
    fixVersion = 10001

^top of fields | ^^top of topic

Anchor
Issue
Issue

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
Code Block
issueKey

Aliases:

Code Block
id
Code Block
issue
Code Block
key
Field Type

ISSUE

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

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

Examples
  • Find the issue with key "ABC-123":

    Code Block
    issueKey = ABC-123 

^top of fields | ^^top of topic

Anchor
Level
Level

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

Info
titleIt 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
Code Block
level
Field Type

SECURITY LEVEL

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions

n/a

Examples
  • Search for issues with a Security Level of "Really High" or "level1":

    Code Block
    level in ("Really High", level1)
  • Search for issues with a Security Level ID of 123:

    Code Block
    level = 123

^top of fields | ^^top of topic

Anchor
originalEstimate
originalEstimate
Anchor
OriginalEstimate
OriginalEstimate

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
Code Block
originalEstimate

Alias:

Code Block
timeOriginalEstimate
Field Type

DURATION

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

n/a

Examples
  • Find issues with an Original Estimate of 1 hour:

    Code Block
    originalEstimate = 1h
  • Find issues with an Original Estimate of more than 2 days:

    Code Block
    originalEstimate > 2d

^top of fields | ^^top of topic

Anchor
Parent
Parent

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
Code Block
parent
Field Type

ISSUE

Supported Operators
Include Page
__JQLOpSBSelectFields(exIS)
nopaneltrue
__JQLOpSBSelectFields(exIS)
Supported Functions

n/a

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

    Code Block
    parent = TEST-1234

^top of fields | ^^top of topic

Anchor
Priority
Priority

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

Info
titleIt 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
Code Block
priority
Field Type

PRIORITY

Supported Operators
Include Page
__JQLOpSBNumericFields(inWASCHANGED)
nopaneltrue
__JQLOpSBNumericFields(inWASCHANGED)
Supported Functions

n/a

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

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

    Code Block
    priority = 10000

^top of fields | ^^top of topic

Anchor
Project
Project

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

Note: this field supports auto-complete.

Syntax
Code Block
project
Field Type

PROJECT

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions

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

Examples
  • Find issues that belong to the Project that has the name "ABC Project":

    Code Block
     project = "ABC Project" 
  • Find issues that belong to the Project that has the key "ABC":

    Code Block
    project = "ABC"
  • Find issues that belong to the Project that has the ID "1234":

    Code Block
    project = 1234

^top of fields | ^^top of topic

Anchor
remainingEstimate
remainingEstimate
Anchor
RemainingEstimate
RemainingEstimate

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
Code Block
remainingEstimate

Alias:

Code Block
timeEstimate
Field Type

DURATION

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

n/a

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

    Code Block
     remainingEstimate > 4h 

^top of fields | ^^top of topic

Anchor
Reporter
Reporter

Reporter

Search for issues that were reported by (i.e. 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
Code Block
reporter
Field Type

USER

Supported Operators
Include Page
__JQLOpSBSelectFields(inWASCHANGED)
nopaneltrue
__JQLOpSBSelectFields(inWASCHANGED)
Supported Functions
Include Page
__JQL Functions supported by User Fields
nopaneltrue
__JQL Functions supported by User Fields
Examples
  • Search for issues that were created by Jill Jones:

    Code Block
    reporter = "Jill Jones"

    or

    Code Block
    reporter = jjones
  • Search for issues that were created by the user with email address "bob@mycompany.com":

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

Anchor
Resolution
Resolution

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

Info
titleIt 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
Code Block
resolution
Field Type

RESOLUTION

Supported Operators
Include Page
__JQLOpSBNumericFields(inWASCHANGED)
nopaneltrue
__JQLOpSBNumericFields(inWASCHANGED)
Supported Functions

n/a

Examples
  • Find issues with a Resolution of "Cannot Reproduce" or "Won't Fix":

    Code Block
     resolution in ("Cannot Reproduce", "Won't Fix")
  • Find issues with a Resolution ID of 5:

    Code Block
    resolution = 5
  • Find issues that do not have a Resolution:

    Code Block
    resolution = unresolved

^top of fields | ^^top of topic

Anchor
Resolved
Resolved
Anchor
ResolutionDate
ResolutionDate
Anchor
resolutionDate
resolutionDate

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

Include Page
__JQL Date Time Formats
nopaneltrue
__JQL Date Time Formats

Note: this field does not support auto-complete.

Syntax
Code Block
resolved

Alias:

Code Block
resolutionDate
Field Type

DATE

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

Include Page
__JQL Functions supported by Date Fields
__JQL Functions supported by Date Fields

Examples
  • Find all issues that were resolved before 31st December 2010:

    Code Block
    resolved <= "2010/12/31"
  • Find all issues that were resolved before 2.00pm on 31st December 2010:

    Code Block
    resolved < "2010/12/31 14:00"
  • Find all issues that were resolved on or before 31st December 2010:

    Code Block
    resolved <= "2011/01/01"
  • Find issues that were resolved in January 2011:

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

    Code Block
    resolved > "2011/01/15" and resolved < "2011/01/16"
  • Find issues that were resolved in the last hour:

    Code Block
    resolved > -1h

^top of fields | ^^top of topic

Anchor
Status
Status

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

Info
titleIt 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
Code Block
status
Field Type

STATUS

Supported Operators
Include Page
__JQLOpSBSelectFields(inWASCHANGED)
nopaneltrue
__JQLOpSBSelectFields(inWASCHANGED)
Supported Functions

n/a

Examples
  • Find issues with a Status of "Open":

    Code Block
     status = Open
  • Find issues with a Status ID of 1:

    Code Block
    status = 1
  • Find issues that currently have, or previously had, a Status of "Open":

    Code Block
     status WAS Open

^top of fields | ^^top of topic

Anchor
Summary
Summary

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
Code Block
summary
Field Type

TEXT

Supported Operators
Include Page
__JQLOpSBTextFields
nopaneltrue
__JQLOpSBTextFields
Supported Functions

n/a

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

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

    Code Block
    summary ~ "\"Error saving file\""

^top of fields | ^^top of topic

Anchor
text
text
Anchor
Text
Text

Text

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

Include Page
__JQL Text Fields
nopaneltrue
__JQL Text Fields

NoteNotes:

Syntax
Code Block
text
Field Type

TEXT

Supported Operators
Include Page
__JQLOpSBTextFields(exISNOT)
nopaneltrue
__JQLOpSBTextFields(exISNOT)
Supported Functions

n/a

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

    Code Block
    text ~ "Fred"

    or

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

    Code Block
    text ~ "\"full screen\""

^top of fields | ^^top of topic

Anchor
Type
Type

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

Info
titleIt 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
Code Block
type

Alias:

Code Block
issueType
Field Type

ISSUE_TYPE

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions

n/a

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

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

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

    Code Block
    issueType = 2

^top of fields | ^^top of topic

Anchor
TimeSpent
TimeSpent
Anchor
timeSpent
timeSpent

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
Code Block
timeSpent
Field Type

DURATION

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

n/a

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

    Code Block
    timeSpent > 5d

^top of fields | ^^top of topic

Anchor
Updated
Updated
Anchor
UpdatedDate
UpdatedDate
Anchor
updatedDate
updatedDate

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

Include Page
__JQL Date Time Formats
nopaneltrue
__JQL Date Time Formats

Note: this field does not support auto-complete.

Syntax
Code Block
updated

Alias:

Code Block
updatedDate
Field Type

DATE

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions
Include Page
__JQL Functions supported by Date Fields
nopaneltrue
__JQL Functions supported by Date Fields
Examples
  • Find issues that were last updated before 12th December 2010:

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

    Code Block
    updated < "2010/12/13"
  • Find all issues that were last updated before 2.00pm on 31st December 2010:

    Code Block
    updated < "2010/12/31 14:00"
  • Find issues that were last updated more than two weeks ago:

    Code Block
    updated < "-2w"
  • Find issues that were last updated on 15 January 2011:

    Code Block
    updated > "2011/01/15" and updated < "2011/01/16"
  • Find issues that were last updated in January 2011:

    Code Block
    updated > "20011/01/01" and updated < "2011/02/01"

^top of fields | ^^top of topic

Anchor
voter
voter
Anchor
Voter
Voter

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
Code Block
voter
Field Type

USER

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions
Include Page
__JQL Functions supported by User Fields
nopaneltrue
__JQL Functions supported by User Fields
Examples
  • Search for issues for which you have voted:

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

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

    Code Block
    voter in membersOf("jira-developers")

^top of fields | ^^top of topic

Anchor
Votes
Votes

Votes

Search for issues with a specified number of votes.

Note: this field does not support auto-complete.

Syntax
Code Block
votes
Field Type

NUMBER

Supported Operators
Include Page
__JQLOpSBNumericFields(exIS)
nopaneltrue
__JQLOpSBNumericFields(exIS)
Supported Functions

n/a

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

    Code Block
    votes >= 12

^top of fields | ^^top of topic

Anchor
watcher
watcher
Anchor
Watcher
Watcher

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
Code Block
watcher
Field Type

USER

Supported Operators
Include Page
__JQLOpSBSelectFields
nopaneltrue
__JQLOpSBSelectFields
Supported Functions
Include Page
__JQL Functions supported by User Fields
nopaneltrue
__JQL Functions supported by User Fields
Examples
  • Search for issues that you are watching:

    Code Block
    watcher = currentUser()
  • Search for issues that the user "jsmith" is watching:

    Code Block
    watcher = "jsmith"
  • Search for issues that are being watched by a member of the group "jira-developers":

    Code Block
    watcher in membersOf("jira-developers")

^top of fields | ^^top of topic

Anchor
Watchers
Watchers

Watchers

Search for issues with a specified number of watchers.

Note: this field does not support auto-complete.

Syntax
Code Block
watchers
Field Type

NUMBER

Supported Operators
Include Page
__JQLOpSBNumericFields(exIS)
nopaneltrue
__JQLOpSBNumericFields(exIS)
Supported Functions

n/a

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

    Code Block
    watchers > 3

^top of fields | ^^top of topic

Anchor
WorkRatio
WorkRatio
Anchor
workRatio
workRatio

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
Code Block
workRatio
Field Type

NUMBER

Supported Operators
Include Page
__JQLOpSBNumericFields
nopaneltrue
__JQLOpSBNumericFields
Supported Functions

n/a

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

    Code Block
     workRatio > 75

^top of fields | ^^top of topic

...