Documentation for JIRA 5.2. 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:
Related topics:
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
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.
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.
A keyword in JQL is a word or phrase that does (or is) any of the following:
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
Ordering by Components or Versions will list the returned issues first by Project and only then by the field's natural order (see JRA-31113).
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 word "issue" and the word "collector":
summary ~ "issue collector"
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.
AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only.)
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 "2011/02/02"
Find issues that were resolved by Joe Smith during 2010:
status WAS "Resolved" BY jsmith DURING ("2010/01/01","2011/01/01")
^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"
.
AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only.)
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"
.
AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only.)
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 "2011/02/02"
^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.
AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only.)
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 "2011/02/02"
^top of operators | ^^top of topic
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:
AFTER "date"
BEFORE "date"
BY "username"
DURING ("date1","date2")
ON "date"
FROM "oldvalue"
TO "newvalue"
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status 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
Only available if you are using GreenHopper 6.0.6 or later.
Search for issues that belong to a particular epic in GreenHopper. The search is based on either the epic's Issue Key or Issue ID (i.e. the number that JIRA automatically allocates to an Issue).
Note: this field does not support auto-complete.
"epic link"
Epic Link Relationship (this is a custom type created by GreenHopper).
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
When used with the IN or NOT IN operators, epic link
supports:
Find issues that belong to epic "Jupiter", which has issue key ANERDS-317:
"epic link" = ANERDS-317
^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
Search for issues that were last viewed on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).
"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.
lastViewed
DATE
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find all issues last viewed before 12th December 2010:
lastViewed < "2010/12/12"
Find all issues last viewed on or before 12th December 2010:
lastViewed <= "2010/12/13"
Find all issues last viewed on 12th December 2010 before 2:00pm:
lastViewed > "2010/12/12" and created < "2010/12/12 14:00"
Find issues last viewed less than one day ago:
lastViewed > "-1d"
Find issues last viewed in January 2011:
lastViewed > "2011/01/01" and created < "2011/02/01"
Find issues last viewed on 15 January 2011:
lastViewed > "2011/01/15" and created < "2011/01/16"
^top of 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
Only available if you are using GreenHopper.
Search for issues that are assigned to a particular sprint in GreenHopper. The search is based on the sprint ID (i.e. the number that JIRA automatically allocates to a sprint).
sprint
Number
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Find issues that belong to sprint 999:
sprint = 999
Find issues that belong to either sprint 1, sprint 3 or sprint 4:
sprint in (1,3,4)
Find issues that are assigned to a sprint:
sprint is not empty
^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.:
Notes:
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
9 Comments
Steve Huang
I'm trying to do a jql query with
summary !~ "\\[ENG\\]"
and this does not work when there is a summary with [ENG] in the summary.
summary ~ "\\[ENG\\]"
doesn't appear to work either.
Anonymous
I'm having this problem as well, this is covered in the bug: https://jira.atlassian.com/browse/JRA-25092
(at this time, the bug is resolved, but a "Fix Version" is not specified)
Dana Frost
I have a similar issue finding things with underscore... According to the docs, you should be able to specify literal characters using the unicode \u005B (left bracket) but when you do, you get the same error. The tokenized search just does not seem to handle reserved token separators very well.
summary ~ "\u005BENG\u005D" should work but you get the same issue... I would like to know hot to deal with token characters in a search in general.
Rodrigo Arruda
Links for function section appear not to be working.
SusanA
Hi, thanks for letting us know. We recently broke this page into two pages, Advanced Searching and Advanced Searching Functions, and it looks like we didn't update the links to point to the new page section: Advanced Searching Functions. I'll take care of this.
Ian Mayoh
Is it just me then? The advanced function links are still not working and the URL in Susan Griffin's comment just seems to cycle back to the same page.
Peter Hill
Same problem for me. I'd like to dig into the advanced searching functions, but I can't seem to find more information about them.
SusanA
Hello. I am sorry it does not appear to be working for you. When I click this "functions" link:
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.
It takes me to this page:
Advanced Searching Functions#function
which is the behavior I would expect. I did an spot check and the other links on this page seem to be behaving correctly for me. If you can point me at a specific link on the page that is still broken, I will be happy to fix it.
Cheers,
Susan
Larry Talley
Here is a link to advanced searching functions for JIRA 6 which may be helpful while the link in this current page is broken: Advanced Searching Functions