Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.
An advanced search allows you to use structured queries to search for JIRA issues. Your search results will be displayed in the Issue Navigator, where you can export them to MS Excel and many other formats. You can also save and subscribe to your advanced searches if you wish.
When you perform an advanced search, you are using the JIRA Query Language (JQL).
A simple query in JQL (also known as a 'clause') consists of a field, followed by an operator, followed by one or more values or functions. For example, the following simple query will find all issues in the "TEST" project:
project = "TEST"
(This example uses the Project field, the EQUALS operator, and the value "TEST"
.)
Be aware that it is not possible to compare two fields.
JQL gives you some SQL-like syntax, such as the ORDER BY SQL keyword and ISNULL() SQL function (i.e. the NULL keyword in JQL). However, JQL is not a database query language. For example, JQL does not have a SELECT
statement.
On this page:
A keyword in JQL is a word or phrase that:
List of keywords:
Used to combine multiple clauses, allowing you to refine your search.
Note that you can use parentheses to control the order in which clauses are executed.
Find all open issues in the "New office" project:
project = "New office" and status = "open"
Find all open, urgent issues that are assigned to jsmith:
status = open and priority = urgent and assignee = jsmith
Find all issues in a particular project that are not assigned to jsmith:
project = JRA and assignee != jsmith
Find all issues for a specific release which consists of different version numbers across several projects:
project in (JRA,CONF) and fixVersion = "3.14"
Find all issues where neither the Reporter nor the Assignee is Jack, Jill or John:
reporter not in (Jack,Jill,John) and assignee not in (Jack,Jill,John)
^top of keywords | ^^top of topic
Used to combine multiple clauses, allowing you to expand your search.
Note that you can use parentheses to control the order in which clauses are executed.
(Note: also see IN, which can be a more convenient way to search for multiple values of a field.)
Find all issues that were created by either jsmith or jbrown:
reporter = jsmith or reporter = jbrown
Find all issues that are overdue or where no due date is set:
duedate < now() or duedate is empty
^top of keywords | ^^top of topic
Used to negate individual clauses or a complex JQL query (a query made up of more than one clause) using parentheses, allowing you to refine your search.
(Note: also see NOT EQUALS ("!="), DOES NOT CONTAIN ("!~"), NOT IN and IS NOT.)
Find all issues that are assigned to any user except jsmith:
not assignee = jsmith
Find all issues that were not created by either jsmith or jbrown:
not (reporter = jsmith or reporter = jbrown)
^top of keywords | ^^top of topic
Used to search for issues where a given field does not have a value. See also NULL.
Note that EMPTY can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.
Find all issues without a DueDate:
duedate = empty
or
duedate is empty
^top of keywords | ^^top of topic
Used to search for issues where a given field does not have a value. See also EMPTY.
Note that NULL can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.
Find all issues without a DueDate:
duedate = null
or
duedate is null
^top of keywords | ^^top of topic
Used to specify the fields by whose values the search results will be sorted.
By default, the field's own sorting order will be used. You can override this by specifying ascending order ("asc
") or descending order ("desc
").
Find all issues without a DueDate, sorted by CreationDate:
duedate = empty order by created
Find all issues without a DueDate, sorted by CreationDate, then by Priority (highest to lowest):
duedate = empty order by created, priority desc
Find all issues without a DueDate, sorted by CreationDate, then by Priority (lowest to highest):
duedate = empty order by created, priority asc
An operator in JQL is one or more symbols or words which compares the value of a field on its left with one or more values (or functions) on its right, such that only true results are retrieved by the clause. Some operators may use the NOT keyword.
List of Operators:
The "=
" operator is used to search for issues where the value of the specified field exactly matches the specified value. (Note: cannot be used with text fields; see the CONTAINS operator instead.)
To find issues where the value of a specified field exactly matches multiple values, use multiple "=
" statements with the AND operator.
Find all issues that were created by jsmith:
reporter = jsmith
Find all issues that were created by John Smith:
reporter = "John Smith"
^top of operators | ^^top of topic
The "!=
" operator is used to search for issues where the value of the specified field does not match the specified value. (Note: cannot be used with text fields; see the DOES NOT MATCH ("!~
") operator instead.)
Note that typing field != value
is the same as typing NOT field = value
, and that field != EMPTY
is the same as field IS_NOT EMPTY
.
The "!=
" operator will not match a field that has no value (i.e. a field that is empty). For example, component != fred
will only match issues that have a component and the component is not "fred". To find issues that have a component other than "fred" or have no component, you would need to type: component != fred or component is empty
.
Find all issues that are assigned to any user except jsmith:
not assignee = jsmith
or:
assignee != jsmith
Find all issues that are not assigned to jsmith:
assignee != jsmith or assignee is empty
Find all issues that were reported by me but are not assigned to me:
reporter = currentUser() and assignee != currentUser()
Find all issues where the Reporter or Assignee is anyone except John Smith:
assignee != "John Smith" or reporter != "John Smith"
Find all issues that are not unassigned:
assignee is not empty
or
assignee != null
^top of operators | ^^top of topic
The ">
" operator is used to search for issues where the value of the specified field is greater than the specified value. Cannot be used with text fields.
Note that the ">
" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.
Find all issues with more than 4 votes:
votes > 4
Find all overdue issues:
duedate < now() and resolution is empty
Find all issues where priority is higher than "Normal":
priority > normal
^top of operators | ^^top of topic
The ">=
" operator is used to search for issues where the value of the specified field is greater than or equal to the specified value. Cannot be used with text fields.
Note that the ">=
" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.
Find all issues with 4 or more votes:
votes >= 4
Find all issues due on or after 31/12/2008:
duedate >= "2008/12/31"
Find all issues created in the last five days:
created >= "-5d"
^top of operators | ^^top of topic
The "<
" operator is used to search for issues where the value of the specified field is less than the specified value. Cannot be used with text fields.
Note that the "<
" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.
Find all issues with less than 4 votes:
votes < 4
^top of operators | ^^top of topic
The "<=
" operator is used to search for issues where the value of the specified field is less than or equal to than the specified value. Cannot be used with text fields.
Note that the "<=
" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.
Find all issues with 4 or fewer votes:
votes <= 4
Find all issues that have not been updated in the past month (30 days):
updated <= "-4w 2d"
^top of operators | ^^top of topic
The "IN
" operator is used to search for issues where the value of the specified field is one of multiple specified values. The values are specified as a comma-delimited list, surrounded by parentheses.
Using "IN
" is equivalent to using multiple EQUALS (=)
statements, but is shorter and more convenient. That is, typing reporter IN (tom, jane, harry)
is the same as typing reporter = "tom" OR reporter = "jane" OR reporter = "harry"
.
Find all issues that were created by either jsmith or jbrown or jjones:
reporter in (jsmith,jbrown,jjones)
Find all issues where the Reporter or Assignee is either Jack or Jill:
reporter in (Jack,Jill) or assignee in (Jack,Jill)
Find all issues in version 3.14 or version 4.2:
affectedVersion in ("3.14", "4.2")
^top of operators | ^^top of topic
The "NOT IN
" operator is used to search for issues where the value of the specified field is not one of multiple specified values.
Using "NOT IN
" is equivalent to using multiple NOT_EQUALS (!=)
statements, but is shorter and more convenient. That is, typing reporter NOT IN (tom, jane, harry)
is the same as typing reporter != "tom" AND reporter != "jane" AND reporter != "harry"
.
The "NOT IN
" operator will not match a field that has no value (i.e. a field that is empty). For example, assignee not in (jack,jill)
will only match issues that have an assignee and the assignee is not "jack" or "jill". To find issues that are assigned to someone other than "jack" or "jill" or are unassigned, you would need to type: assignee not in (jack,jill) or assignee is empty
.
Find all issues where the Assignee is someone other than Jack, Jill or John:
assignee not in (Jack,Jill,John)
Find all issues where the Assignee is not Jack, Jill or John:
assignee not in (Jack,Jill,John) or assignee is empty
Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D':
FixVersion not in (A, B, C, D)
Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D', or has not been specified:
FixVersion not in (A, B, C, D) or FixVersion is empty
^top of operators | ^^top of topic
The "~
" operator is used to search for issues where the value of the specified field matches the specified value (either an exact match or a "fuzzy" match — see examples below). For use with text fields only, i.e.:
Note: when using the "~
" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.
Find all issues where the Summary contains the word "win" (or simple derivatives of that word, such as "wins"):
summary ~ win
Find all issues where the Summary contains a wild-card match for the word "win":
summary ~ "win*"
Find all issues where the Summary contains the exact phrase "full screen" (see Reserved Characters for details on how to escape quote-marks and other special characters):
summary ~ "\"full screen\""
^top of operators | ^^top of topic
The "!~
" operator is used to search for issues where the value of the specified field is not a "fuzzy" match for the specified value. For use with text fields only, i.e.:
Note: when using the "!~
" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.
Find all issues where the Summary does not contain the word "run" (or derivatives of that word, such as "running" or "ran"):
summary !~ run
^top of operators | ^^top of topic
The "IS
" operator can only be used with EMPTY or NULL. That is, it is used to search for issues where the specified field has no value.
Note that not all fields are compatible with this operator; see the individual field reference for details.
Find all issues that have no Fix Version:
fixVersion is empty
or
fixVersion is null
^top of operators | ^^top of topic
The "IS NOT
" operator can only be used with EMPTY or NULL. That is, it is used to search for issues where the specified field has a value.
Note that not all fields are compatible with this operator; see the individual field reference for details.
Find all issues that have one or more votes:
votes is not empty
or
votes is not null
^top of operators | ^^top of topic
The "WAS
" operator is used to find issues that currently have, or previously had, the specified value for the specified field.
BY "username"
BEFORE "date"
AFTER "date"
ON "date"
DURING ("date1","date2")
(Note: this operator can only be used with the Status, Reporter and Assignee fields. From JIRA 4.4.3, this operator can also be used with the Fix Version, Priority and Resolution fields.)
Find issues that currently have, or previously had, a status of 'In Progress':
status WAS "In Progress"
Find issues that were resolved by Joe Smith before 2nd February:
status WAS "Resolved" BY jsmith BEFORE "02/02/2011"
Find issues that were resolved by Joe Smith during 2010:
status WAS "Resolved" BY jsmith DURING ("01/01/2010","01/01/2011")
^top of operators | ^^top of topic
The "WAS IN
" operator is used to find issues that currently have, or previously had, any of multiple specified values for the specified field. The values are specified as a comma-delimited list, surrounded by parentheses.
Using "WAS IN
" is equivalent to using multiple WAS
statements, but is shorter and more convenient. That is, typing status WAS IN ('Resolved', 'Closed')
is the same as typing status WAS "Resolved" OR status WAS "Closed"
.
BY "username"
BEFORE "date"
AFTER "date"
ON "date"
DURING ("date1","date2")
(Note: this operator can only be used with the Status, Reporter and Assignee fields. From JIRA 4.4.3, this operator can also be used with the Fix Version, Priority and Resolution fields.)
Find all issues that currently have, or previously had, a status of 'Resolved' or 'In Progress':
status WAS IN ("Resolved","In Progress")
^top of operators | ^^top of topic
The "WAS NOT IN
" operator is used to search for issues where the value of the specified field has never been one of multiple specified values.
Using "WAS NOT IN
" is equivalent to using multiple WAS_NOT
statements, but is shorter and more convenient. That is, typing status WAS NOT IN ("Resolved","In Progress")
is the same as typing status WAS NOT "Resolved" AND status WAS NOT "In Progress"
.
BY "username"
BEFORE "date"
AFTER "date"
ON "date"
DURING ("date1","date2")
(Note: this operator can only be used with the Status, Reporter and Assignee fields. From JIRA 4.4.3, this operator can also be used with the Fix Version, Priority and Resolution fields.)
Find issues that have never had a status of 'Resolved' or 'In Progress':
status WAS NOT IN ("Resolved","In Progress")
Find issues that did not have a status of 'Resolved' or 'In Progress' before 2nd February:
status WAS NOT IN ("Resolved","In Progress") BEFORE "02/02/2011"
^top of operators | ^^top of topic
The "WAS NOT
" operator is used to find issues that have never had the specified value for the specified field.
BY "username"
BEFORE "date"
AFTER "date"
ON "date"
DURING ("date1","date2")
(Note: this operator can only be used with the Status, Reporter and Assignee fields. From JIRA 4.4.3, this operator can also be used with the Fix Version, Priority and Resolution fields.)
Find issues that do not have, and has never had, a status of 'In Progress':
status WAS NOT "In Progress"
Find issues that did not have a status of 'In Progress' before 2nd February:
status WAS NOT "In Progress" BEFORE "02/02/2011"
^top of operators | ^^top of topic
This feature is only available in JIRA 4.4.3 and later.
The "CHANGED
" operator is used to find issues that have a value which had changed for the specified field.
This operator has the following optional predicates:
FROM "oldvalue"
TO "newvalue"
BY "username"
ON "date"
DURING ("date1","date2")
BEFORE "date"
AFTER "date"
(Note: This operator can currently be used with the Status, Assignee, Priority, Reporter, Resolution and Fix Version fields only.)
Find issues whose assignee had changed:
assignee CHANGED
Find issues whose status had changed from 'In Progress' back to 'Open':
status CHANGED FROM "In Progress" TO "Open"
Find issues whose priority was changed by user 'freddo' after the start and before the end of the current week.
priority CHANGED BY freddo BEFORE endOfWeek() AFTER startOfWeek()
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:
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.
affectedVersion
VERSION
= | != | ~ | !~ | > | >= | < | <= | 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.
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
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.
assignee
USER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the EQUALS and NOT EQUALS operators, this field supports:
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
Search for issues that belong to projects in a particular Category.
Note: this field supports auto-complete.
category
CATEGORY
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find issues that belong to projects in the "Alphabet Projects" Category:
category = "Alphabet Projects"
^top of fields | ^^top of topic
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.
comment
TEXT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
component
COMPONENT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the IN and NOT IN operators, component
supports:
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
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).
"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.
created
Alias:
createdDate
DATE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find all issues created before 12th December 2010:
created < "2010/12/12"
Find all issues created on or before 12th December 2010:
created <= "2010/12/13"
Find all issues created on 12th December 2010 before 2:00pm:
created > "2010/12/12" and created < "2010/12/12 14:00"
Find issues created less than one day ago:
created > "-1d"
Find issues created in January 2011:
created > "2011/01/01" and created < "2011/02/01"
Find issues created on 15 January 2011:
created > "2011/01/15" and created < "2011/01/16"
^top of fields | ^^top of topic
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:
CustomFieldName
Alias:
cf[CustomFieldID]
Depends on the Custom Field's configuration
Different types of Custom Fields support different operators. For the default Custom Field Types, the following operators are supported:
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Different types of Custom Fields support different functions. For the default Custom Field Types, the following functions are supported:
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
Search for issues where the Description contains particular text.
JIRA text-search syntax can be used.
Note: this field does not support auto-complete.
description
TEXT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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).
"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.
due
Alias:
dueDate
DATE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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
Search for issues where the Environment contains particular text.
JIRA text-search syntax can be used.
Note: this field does not support auto-complete.
environment
TEXT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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:
filter
Aliases:
request
savedFilter
searchRequest
FILTER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
fixVersion
VERSION
= | != | ~ | !~ | > | >= | < | <= | 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.
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
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.
issueKey
Aliases:
id
issue
key
ISSUE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the IN or NOT IN operators, issueKey
supports:
Find the issue with key "ABC-123":
issueKey = ABC-123
^top of fields | ^^top of topic
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.
level
SECURITY LEVEL
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
originalEstimate
Alias:
timeOriginalEstimate
DURATION
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
parent
ISSUE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find issues that are sub-tasks of issue TEST-1234:
parent = TEST-1234
^top of fields | ^^top of topic
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.
priority
PRIORITY
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
project
PROJECT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the IN and NOT IN operators, project
supports:
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
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.
remainingEstimate
Alias:
timeEstimate
DURATION
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find issues with a Remaining Estimate of more than 4 hours:
remainingEstimate > 4h
^top of fields | ^^top of topic
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.
reporter
USER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the EQUALS and NOT EQUALS operators, this field supports:
Search for issues that were created by Jill Jones:
reporter = "Jill Jones"
or
reporter = jjones
Search for issues that were created 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
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.
resolution
RESOLUTION
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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).
"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.
resolved
Alias:
resolutionDate
DATE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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
^top of fields | ^^top of topic
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.
status
STATUS
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
Search for issues where the Summary contains particular text.
JIRA text-search syntax can be used.
Note: this field does not support auto-complete.
summary
TEXT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
This is a "master-field" that allows you to search all text fields, i.e.:
Note: The text
master-field can only be used with the CONTAINS operator ("~
" and "!~
").
text
TEXT
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
type
Alias:
issueType
ISSUE_TYPE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
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
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.
timeSpent
DURATION
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find issues where the Time Spent is more than 5 days:
timeSpent > 5d
^top of fields | ^^top of topic
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).
"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.
updated
Alias:
updatedDate
DATE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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"
^top of fields | ^^top of topic
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.
voter
USER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the EQUALS and NOT EQUALS operators, this field supports:
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
Search for issues with a specified number of votes.
Note: this field does not support auto-complete.
votes
NUMBER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find all issues that have 12 or more votes:
votes >= 12
^top of fields | ^^top of topic
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.
watcher
USER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the EQUALS and NOT EQUALS operators, this field supports:
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
Search for issues with a specified number of watchers.
Note: this field does not support auto-complete.
watchers
NUMBER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find all issues that are being watched by more than 3 people:
watchers > 3
^top of fields | ^^top of topic
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.
workRatio
NUMBER
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
n/a
Find issues on which more than 75% of the Original Estimate has been spent:
workRatio > 75
A function in JQL appears as a word followed by parentheses which may contain one or more explicit values or JIRA fields. In a clause, a function is preceded by an operator, which in turn is preceded by a field. A function performs a calculation on either specific JIRA data or the function's content in parentheses, such that only true results are retrieved by the function and then again by the clause in which the function is used.
List of Functions:
Search for issues that match the selected values of a 'cascading select' custom field.
The parentOption parameter matches against the first tier of options in the cascading select field. The childOption parameter matches against the second tier of options in the cascading select field, and is optional.
The keyword "none"
can be used to search for issues where either or both of the options have no value.
cascadeOption(parentOption)
or
cascadeOption(parentOption,childOption)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues where a custom field ("Location") has the value "USA" for the first tier and "New York" for the second tier:
location in cascadeOption("USA","New York")
Find issues where a custom field ("Location") has the value "USA" for the first tier and any value (or no value) for the second tier:
location in cascadeOption("USA")
Find issues where a custom field ("Location") has the value "USA" for the first tier and no value for the second tier:
location in cascadeOption("USA",none)
Find issues where a custom field ("Location") has no value for the first tier and no value for the second tier:
location in cascadeOption(none)
Find issues where a custom field ("Referrer") has the value "none" for the first tier and "none" for the second tier:
referrer in cascadeOption("\"none\"","\"none\"")
Find issues where a custom field ("Referrer") has the value "none" for the first tier and no value for the second tier:
referrer in cascadeOption("\"none\"",none)
^top of functions | ^^top of topic
Find issues in components that are lead by a specific user.
You can optionally specify a user, or if the user is omitted the current user (i.e. you) will be used.
Note that if you are not logged in to JIRA, a user must be specified.
componentsLeadByUser()
or
componentsLeadByUser(username)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find open issues in components that are lead by you:
component in componentsLeadByUser() AND status = Open
Find open issues in components that are lead by Bill:
component in componentsLeadByUser(bill) AND status = Open
^top of functions | ^^top of topic
Perform searches based on the time at which the current user's session began. See also lastLogin.
currentLogin()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues that have been created during my current session:
created > currentLogin()
^top of functions | ^^top of topic
Perform searches based on the currently logged-in user.
Note that this function can only be used by logged-in users. So if you are creating a saved filter that you expect to be used by anonymous users, do not use this function.
currentUser()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that are assigned to me:
assignee = currentUser()
Find issues that were reported to me but are not assigned to me:
reporter = currentUser() and assignee != currentUser()
^top of functions | ^^top of topic
Perform searches based on the earliest unreleased version (i.e. next version that is due to be released) of a specified project. See also unreleasedVersions.
Note that the "earliest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.
earliestUnreleasedVersion(project)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues whose FixVersion is the earliest unreleased version of the ABC project:
fixVersion = earliestUnreleasedVersion(ABC)
Find issues that relate to the earlist unreleased version of the ABC project:
affectedVersion = earliestUnreleasedVersion(ABC) or fixVersion = earliestUnreleasedVersion(ABC)
^top of functions | ^^top of topic
Perform searches based on the end of the current day. See also endOfWeek, endOfMonth and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear.
endOfDay()
or
endOfDay("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
endOfDay("+1")
is the same as endOfDay("+1d")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues due by the end of today:
due < endOfDay()
Find issues due by the end of tomorrow:
due < endOfDay("+1")
^top of functions | ^^top of topic
Perform searches based on the end of the current month. See also endOfDay, endOfWeek and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear.
endOfMonth()
or
endOfMonth("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
endOfMonth("+1")
is the same as endOfMonth("+1M")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues due by the end of this month:
due < endOfMonth()
Find issues due by the end of next month:
due endOfMonth("+1")
Find issues due by the 15th of next month:
due endOfMonth("+15d")
^top of functions | ^^top of topic
Perform searches based on the end of the current week. See also endOfDay, endOfMonth and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear.
For the endOfWeek() function the result depends upon your locale. For example, in Europe the first day of the week is generally considered to be Monday, while in the USA it is considered to be Sunday.
endOfWeek()
or
endOfWeek("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues due by the end of this week:
due < endOfWeek()
Find issues due by the end of next week:
due < endOfWeek("+1")
^top of functions | ^^top of topic
Perform searches based on the end of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear.
startOfYear()
or
startOfYear("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
endOfYear("+1")
is the same as endofYear("+1y")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues due by the end of this year:
due < endOfYear()
Find issues due by the end of March next year:
due < endOfYear("+3M")
^top of functions | ^^top of topic
Find issues that you have recently viewed, i.e. issues that are in the 'Recent Issues' section of the 'Issues' drop-down menu.
Note:
issueHistory()
returns up to 50 issues, whereas the 'Recent Issues' drop-down returns only 5.issueHistory()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues which I have recently viewed, that are assigned to me:
issue in issueHistory() AND assignee = currentUser()
^top of functions | ^^top of topic
Perform searches based on the time at which the current user's previous session began. See also currentLogin.
currentLogin()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues that have been created during my last session:
created > lastLogin()
^top of functions | ^^top of topic
Perform searches based on the latest released version (i.e. the most recent version that has been released) of a specified project. See also releasedVersions().
Note that the "latest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.
latestReleasedVersion(project)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues whose FixVersionis the latest released version of the ABC project:
fixVersion = latestReleasedVersion(ABC)
Find issues that relate to the latest released version of the ABC project:
affectedVersion = latestReleasedVersion(ABC) or fixVersion = latestReleasedVersion(ABC)
^top of functions | ^^top of topic
Perform searches based on issues which are linked to a specified issue.
You can optionally restrict the search to links of a particular type. Note that LinkType is case-sensitive.
linkedIssues(issueKey)
or
linkedIssues(issueKey,linkType)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that are linked to a particular issue:
issue in linkedIssues(ABC-123)
Find issues that are linked to a particular issue via a particular type of link:
issue in linkedIssues(ABC-123,"is duplicated by")
^top of functions | ^^top of topic
Perform searches based on the members of a particular group.
membersOf(Group)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues where the Assignee is a member of the group "jira-developers":
assignee in membersOf("jira-developers")
Search through multiple groups and a specific user, e.g:
reporter in membersOf("jira-developers") or reporter in membersOf("jira-administrators") or reporter=jsmith
Search for a particular group, but exclude a particular member or members, e.g.:
assignee in membersOf(QA) and assignee not in ("John Smith","Jill Jones")
Exclude members of a particular group:
assignee not in membersOf(QA)
^top of functions | ^^top of topic
Perform searches based on the current time.
now()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find issues that are overdue:
duedate < now() and status not in (closed, resolved)
^top of functions | ^^top of topic
Find issues in projects that are lead by a specific user.
You can optionally specify a user, or if the user is omitted the current user will be used.
Note that if you are not logged in to JIRA, a user must be specified.
projectsLeadByUser()
or
projectsLeadByUser(username)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find open issues in projects that are lead by you:
project in projectsLeadByUser() AND status = Open
Find open issues in projects that are lead by Bill:
project in projectsLeadByUser(bill) AND status = Open
^top of functions | ^^top of topic
Find issues in projects where you have a specific permission.
Note: This function operates at the project level. This means that if a permission (e.g. "Edit Issues") is granted to the reporter of issues in a project, then you may see some issues returned where you are
not the reporter and therefore don't have the permission specified.
Also note that this function is only available if you are logged in to JIRA.
projectsWhereUserHasPermission(permission)
For the permission
parameter you can specify any of the following:
Project Permissions |
Explanation |
---|---|
Administer Projects |
Permission to administer a project in JIRA. This includes the ability to edit project role membership, project components, project versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description'). |
Browse Projects |
Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted via Issue Security). Many other permissions are dependent on this permission, e.g. the 'Work On Issues' permission is only effective for users who also have the 'Browse Projects' permission. |
View Version Control |
Permission to view the version control information (e.g. CVS, Subversion, FishEye, etc) for an issue. Note that for CVS, to view the Version Control information the project needs to be associated with at least one Repository. |
View (Read-Only) Workflow |
Permission to view the project's 'read-only' workflow when viewing an issue. This permission provides the 'View Workflow' link against the 'Status' field of the 'View Issue' page. |
Issue Permissions |
Explanation |
Assign Issues |
Permission to assign issues to users. (See also Assignable User permission below) |
Assignable User |
Permission to be assigned issues. (Note that this does not include the ability to assign issues; see Assign Issue permission above). |
Close Issues |
Permission to close issues. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission. |
Create Issues |
Permission to create issues in the project. (Note that the Create Attachments permission is required in order to create attachments.) Includes the ability to create sub-tasks (if sub-tasks are enabled). |
Delete Issues |
Permission to delete issues. Think carefully about which groups or project roles you assign this permission to; usually it will only be given to administrators. Note that deleting an issue will delete all of its comments and attachments, even if the user does not have the Delete Comments or Delete Attachments permissions. However, the Delete Issues permission does not include the ability to delete individual comments or attachments. |
Edit Issues |
Permission to edit issues (excluding the 'Due Date' field — see the Schedule Issues permission). Includes the ability to convert issues to sub-tasks and vice versa (if sub-tasks are enabled). Note that the Delete Issue permission is required in order to delete issues. The Edit Issue permission is usually given to any groups or project roles who have the Create Issue permission (perhaps the only exception to this is if you give everyone the ability to create issues — it may not be appropriate to give everyone the ability to edit too). Note that all edits are recorded in the Issue Change History for audit purposes. |
Link Issues |
Permission to link issues together. (Only relevant if Issue Linking is enabled). |
Modify Reporter |
Permission to modify the 'Reporter' of an issue. This allows a user to create issues 'on behalf of' someone else. This permission should generally only be granted to administrators. |
Move Issues |
Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission. |
Resolve Issues |
Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission. |
Schedule Issues |
Permission to schedule an issue — that is, set and edit the 'Due Date' of an issue. |
Set Issue Security |
Permission to set the security level on an issue to control who can access the issue. Only relevant if issue security has been enabled. |
Voters & Watchers Permissions |
Explanation |
Manage Watcher List |
Permission to manage (i.e. view/add/remove users to/from) the watcher list of an issue. |
View Voters and Watchers |
Permission to view the voter list and watcher list of an issue. Also see the Manage Watcher List permission. |
Comments Permissions |
Explanation |
Add Comments |
Permission to add comments to issues. Note that this does not include the ability to edit or delete comments. |
Delete All Comments |
Permission to delete any comments, regardless of who added them. |
Delete Own Comments |
Permission to delete comments that were added by the user. |
Edit All Comments |
Permission to edit any comments, regardless of who added them. |
Edit Own Comments |
Permission to edit comments that were added by the user. |
Attachments Permissions |
Explanation |
Create Attachments |
Permission to attach files to an issue. (Only relevant if attachments are enabled). Note that this does not include the ability to delete attachments. |
Delete All Attachments |
Permission to delete any attachments, regardless of who added them. |
Delete Own Attachments |
Permission to delete attachments that were added by the user. |
Time Tracking Permissions |
Explanation |
Work On Issues |
Permission to log work against an issue, i.e. create a worklog entry. (Only relevant if Time Tracking is enabled). |
Delete All Worklogs |
Permission to delete any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission. |
Delete Own Worklogs |
Permission to delete worklog entries that were added by the user. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission. |
Edit All Worklogs |
Permission to edit any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission. |
Edit Own Worklogs |
Permission to edit worklog entries that were added by the user. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission. |
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find open issues in projects where you have the "Resolve Issues" permission:
project in projectsWhereUserHasPermission("Resolve Issues") AND status = Open
^top of functions | ^^top of topic
Find issues in projects where you have a specific role.
Note that this function is only available if you are logged in to JIRA.
projectsWhereUserHasRole(rolename)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find open issues in projects where you have the "Developers" role:
project in projectsWhereUserHasRole("Developers") AND status = Open
^top of functions | ^^top of topic
Perform searches based on the released versions (i.e. versions that your JIRA administrator has released) of a specified project.
You can also search on the released versions of all projects, by omitting the project parameter.
See also latestReleasedVersion().
releasedVersions()
or
releasedVersions(project)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues whose FixVersionis a released version of the ABC project:
fixVersion in releasedVersions(ABC)
Find issues that relate to released versions of the ABC project:
affectedVersion in releasedVersions(ABC)
or
fixVersion in releasedVersions(ABC)
^top of functions | ^^top of topic
Perform searches based on "standard" Issue Types, that is, search for issues which are not sub-tasks.
See also subtaskIssueTypes().
standardIssueTypes()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that are not subtasks (i.e. issues whose Issue Type is a standard issue type, not a subtask issue type):
issuetype in standardIssueTypes()
^top of functions | ^^top of topic
Perform searches based on the start of the current day. See also startOfWeek, startOfMonth and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear.
startOfDay()
or
startOfDay("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
startOfDay("+1")
is the same as startofDay("+1d")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find new issues created since the start of today:
created > startOfDay()
Find new issues created since the start of yesterday:
created > startOfDay("-1")
Find new issues created in the last three days:
created > startOfDay("-3d")
^top of functions | ^^top of topic
Perform searches based on the start of the current month. See also startOfDay, startOfWeek and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear.
startOfMonth()
or
startOfMonth("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
startOfMonth("+1")
is the same as startofMonth("+1M")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find new issues since the start of this month:
created > startOfMonth()
Find new issues since the start of last month:
created > startOfMonth("-1")
Find new issues since the 15th of this month:
created > startOfMonth("+14d")
^top of functions | ^^top of topic
Perform searches based on the start of the current week. See also startOfDay, startOfMonth and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear.
For the startOfWeek() function the result depends upon your locale. For example, in Europe the first day of the week is generally considered to be Monday, while in the USA it is considered to be Sunday.
startOfWeek()
or
startOfWeek("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find new issues since the start of this week:
created > startOfWeek()
Find new issues since the start of last week:
created > startOfWeek("-1")
^top of functions | ^^top of topic
Perform searches based on the start of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear.
startOfYear()
or
startOfYear("inc")
where inc
is an optional increment of (+/-)nn(y|M|w|d|h|m)
startOfYear("+1")
is the same as startofYear("+1y")
.(+/-)
sign is omitted, plus is assumed.= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(only in | (only in | (only in | (only in | (only in predicate) |
Find new issues since the start of this year:
created > startOfYear()
Find new issues since the start of last year:
created > startOfYear("-1")
^top of functions | ^^top of topic
Perform searches based on issues which are sub-tasks.
See also standardIssueTypes().
subtaskIssueTypes()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that are subtasks (i.e. issues whose Issue Type is a subtask issue type):
issuetype in subtaskIssueTypes()
^top of functions | ^^top of topic
Perform searches based on the unreleased versions (i.e. versions that your JIRA administrator has not yet released) of a specified project.
You can also search on the unreleased versions of all projects, by omitting the project parameter.
See also earliestUnreleasedVersion().
unreleasedVersions()
or
unreleasedVersions(project)
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues whose FixVersionis an unreleased version of the ABC project:
fixVersion in unreleasedVersions(ABC)
Find issues that relate to unreleased versions of the ABC project:
affectedVersion in unreleasedVersions(ABC)
or
fixVersion in unreleasedVersions(ABC)
^top of functions | ^^top of topic
Perform searches based on issues for which you have voted. Also see the Voter field.
Note that this function can only be used by logged-in users.
votedIssues()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that you have voted for:
issue in votedIssues()
^top of functions | ^^top of topic
Perform searches based on issues which you are watching. Also see the Watcher field.
Note that this function can only be used by logged-in users.
watchedIssues()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that you are watching:
issue in watchedIssues()
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that you have recently viewed:
issue in issueHistory()
You can use parentheses in complex JQL statements to enforce the precedence of operators.
For example, if you want to find all resolved issues in the SysAdmin project as well as all issues (any status, any project) currently assigned to the system administrator (bobsmith), you can use parentheses to enforce the precedence of the boolean operators in your query, i.e.:
(status=resolved AND project=SysAdmin) OR assignee=bobsmith
Note that if you do not use parentheses, the statement will be evaluated left-to-right.
You can also use parentheses to group clauses, so that you can apply the NOT operator to the group.
You can use Lucene's text-searching features when performing searches on the following fields, using the CONTAINS operator:
For details, please see the page on Performing Text Searches.
As you type your query, JIRA will recognise the context and offer a list of "auto-complete" suggestions as follows:
The list of auto-complete suggestions is displayed alphabetically and includes the first 15 matches. Note that auto-complete suggestions are not offered for function parameters.
Please note:
Auto-complete suggestions are not offered for all fields. Check the fields reference to see which fields support auto-complete.
...JIRA will offer a list of all available fields, e.g.:
...JIRA will offer a list of matching fields, e.g.:
...JIRA will offer a list of valid operators, e.g.:
...JIRA will offer a list of valid values, e.g.:
...JIRA will offer a list of valid values (if your field supports this) and valid functions for the field/operator combination, e.g.:
In general, a query created using 'Simple Search' will be able to be translated to 'Advanced Search' (i.e. JQL), and back again.
However, a query created using 'Advanced Search' may not be able to be translated to 'Simple Search', particular if:
project in (A, B)
)(project = JRA OR project = CONF)
is equivalent to this query:(project in (JRA, CONF))
, only the second query will be translated.fixVersion = "4.0"
, without the AND project=JRA
). This is especially tricky with custom fields since they can be configured on a Project/Issue Type basis. The general rule of thumb is
JQL has a list of reserved characters:
" "
)"+"
"."
","
";"
"?"
"|"
"*"
"/"
"%"
"^"
"$"
"#"
"@"
"["
"]"
If you wish to use these characters in queries, you need to:
'
) or double quote-marks ("
));The text fields are:
For example:
version = "[example]"
version = "4.2"
summary ~ "\\[example\\]"
summary ~ "4.2"
JQL has a list of reserved words. These words need to be surrounded by quote-marks if you wish to use them in queries:
"abort", "access", "add", "after", "alias", "all", "alter", "and", "any", "as", "asc",
"audit", "avg", "before", "begin", "between", "boolean", "break", "by", "byte", "catch", "cf",
"char", "character", "check", "checkpoint", "collate", "collation", "column", "commit", "connect", "continue",
"count", "create", "current", "date", "decimal", "declare", "decrement", "default", "defaults", "define", "delete",
"delimiter", "desc", "difference", "distinct", "divide", "do", "double", "drop", "else", "empty", "encoding",
"end", "equals", "escape", "exclusive", "exec", "execute", "exists", "explain", "false", "fetch", "file", "field",
"first", "float", "for", "from", "function", "go", "goto", "grant", "greater", "group", "having",
"identified", "if", "immediate", "in", "increment", "index", "initial", "inner", "inout", "input", "insert",
"int", "integer", "intersect", "intersection", "into", "is", "isempty", "isnull", "join", "last", "left",
"less", "like", "limit", "lock", "long", "max", "min", "minus", "mode", "modify",
"modulo", "more", "multiply", "next", "noaudit", "not", "notin", "nowait", "null", "number", "object",
"of", "on", "option", "or", "order", "outer", "output", "power", "previous", "prior", "privileges",
"public", "raise", "raw", "remainder", "rename", "resource", "return", "returns", "revoke", "right", "row",
"rowid", "rownum", "rows", "select", "session", "set", "share", "size", "sqrt", "start", "strict",
"string", "subtract", "sum", "synonym", "table", "then", "to", "trans", "transaction", "trigger", "true",
"uid", "union", "unique", "update", "user", "validate", "values", "view", "when", "whenever", "where",
"while", "with"
You can use either single quote-marks ('
) or double quote-marks ("
).
(Note for JIRA administrators: this list is hard coded in the JqlStringSupportImpl.java
file.)