JIRA 4.3 : Advanced Searching
This page last changed on Mar 21, 2011 by rosie@atlassian.com.
On this page: What is an Advanced Search?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. A query consists of a field, followed by an operator, followed by a value or function. For example, the following query will find all issues in the "TEST" project: project = "TEST" (This example uses the Project field, the EQUALS operator, and the value "TEST".) Note that it is not possible to compare two fields. When you perform an advanced search, you are using the JIRA Query Language (JQL). JQL gives you some SQL-like statements, such as > and NULL. It is not, however, a database query language; for example, JQL does not have a SELECT statement. How to Perform an Advanced Search
Keywords ReferenceANDUsed to combine multiple statements, allowing you to refine your search. Note that you can use parentheses to control the order in which statements are executed. Examples
ORUsed to combine multiple statements, allowing you to expand your search. Note that you can use parentheses to control the order in which statements are executed. (Note: also see IN, which can be a more convenient way to search for multiple values of a field.) Examples
NOTUsed to negate individual operators or entire statements of a query, allowing you to refine your search. Note that you can use parentheses to control the order in which statements are executed. (Note: also see NOT_EQUALS ("!="), DOES_NOT_CONTAIN ("!~"), NOT_IN and IS_NOT.) Examples
EMPTYUsed 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. Examples
NULLUsed 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. Examples
ORDER BYUsed 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"). Examples
Operators ReferenceEQUALS: =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. Examples
NOT EQUALS: !=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. Examples
GREATER THAN: >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. Examples
GREATER THAN EQUALS: >=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. Examples
LESS THAN: <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. Examples
LESS THAN EQUALS: <=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. Examples
INThe "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". Examples
NOT INThe "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. Examples
CONTAINS: ~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. Examples
DOES NOT CONTAIN: !~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. Examples
ISThe "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. Examples
IS NOTThe "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. Examples
WASThe "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field. Unable to render {include} Couldn't find a page to include called: __JQL WAS Parameters
Note that this operator will match the value name (e.g. "Resolved") that was configured in your system at the time that the field was changed. Also note that it will match the value name, not the value ID — that is, it will match "Resolved" but not "4". (Note: this operator can currently be used with the Status field only.) Examples
WAS INThe "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". Unable to render {include} Couldn't find a page to include called: __JQL WAS Parameters
Note that this operator will match the value name (e.g. "Resolved") that was configured in your system at the time that the field was changed. Also note that it will match the value name, not the value ID — that is, it will match "Resolved" but not "4". (Note: this operator can currently be used with the Status field only.) Examples
WAS NOT INThe "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". Unable to render {include} Couldn't find a page to include called: __JQL WAS Parameters
Note that this operator will match the value name (e.g. "Resolved") that was configured in your system at the time that the field was changed. Also note that it will match the value name, not the value ID — that is, it will match "Resolved" but not "4". (Note: this operator can currently be used with the Status field only.) Examples
WAS NOTThe "WAS NOT" operator is used to find issues that have never had the specified value for the specified field. Unable to render {include} Couldn't find a page to include called: __JQL WAS Parameters
Note that this operator will match the value name (e.g. "Resolved") that was configured in your system at the time that the field was changed. Also note that it will match the value name, not the value ID — that is, it will match "Resolved" but not "4". (Note: this operator can currently be used with the Status field only.) Examples
Fields Reference
Affected VersionSearch for issues that are assigned to a particular Affects Version(s). You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).
Note: this field supports auto-complete. SyntaxaffectedVersion Field TypeVERSION Supported Operators
Note that the comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order. Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: Examples
AssigneeSearch 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. Syntaxassignee Field TypeUSER Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: When used with the EQUALS and NOT_EQUALS operators, this field supports: Examples
CategorySearch for issues that belong to projects in a particular Category. Note: this field supports auto-complete. Syntaxcategory Field TypeCATEGORY Supported Operators
Supported Functionsn/a Examples
CommentSearch 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. Syntaxcomment Field TypeTEXT Supported Operators
Supported Functionsn/a Examples
ComponentSearch for issues that belong to a particular component(s) of a project. You can search by component name or component ID (i.e. the number that JIRA automatically allocates to a component).
Note: this field supports auto-complete. Syntaxcomponent Field TypeCOMPONENT Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, component supports: Examples
CreatedSearch 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. Use one of the following formats: "yyyy/MM/dd HH:mm" 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. Syntaxcreated Alias: createdDate Field TypeDATE Supported Operators
Supported FunctionsWhen used with the EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_EQUALS, LESS_THAN or LESS_THAN_EQUALS operators, this field supports:
Examples
Custom FieldOnly applicable if your JIRA administrator has created one or more Custom Fields. Search for issues where a particular Custom Field has a particular value. You can search by Custom Field name or Custom Field ID (i.e. the number that JIRA automatically allocates to an Custom Field).
Note:
SyntaxCustomFieldName Alias: cf[CustomFieldID] Field TypeDepends on the Custom Field's configuration Supported OperatorsDifferent types of Custom Fields support different operators. For the default Custom Field Types, the following operators are supported:
Supported FunctionsDifferent types of Custom Fields support different functions. For the default Custom Field Types, the following functions are supported:
Examples
DescriptionSearch for issues where the Description contains particular text. JIRA text-search syntax can be used. Note: this field does not support auto-complete. Syntaxdescription Field TypeTEXT Supported Operators
Supported Functionsn/a Examples
DueSearch for issues that were due on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Use one of the following formats: "yyyy/MM/dd HH:mm" 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 that Due Date relates to the date only (not to the time). Note: this field does not support auto-complete. Syntaxdue Alias: dueDate Field TypeDATE Supported Operators
Supported FunctionsWhen used with the EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_EQUALS, LESS_THAN or LESS_THAN_EQUALS operators, this field supports:
Examples
EnvironmentSearch for issues where the Environment contains particular text. JIRA text-search syntax can be used. Note: this field does not support auto-complete. Syntaxenvironment Field TypeTEXT Supported Operators
Supported Functionsn/a Examples
FilterYou can use a saved filter to narrow your search. You can search by filter name or filter ID (i.e. the number that JIRA automatically allocates to a saved filter).
Note:
Field TypeFILTER Supported Operators
Supported Functionsn/a Examples
Fix VersionSearch 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).
Note: this field supports auto-complete. SyntaxfixVersion Field TypeVERSION Supported Operators
Note that the comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order. Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: Examples
Issue KeySearch 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. SyntaxissueKey Aliases: id issue key Field TypeISSUE Supported Operators
Supported FunctionsWhen used with the IN or NOT_IN operators, issueKey supports: Examples
LevelOnly 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).
Note: this field supports auto-complete. Syntaxlevel Field TypeSECURITY LEVEL Supported Operators
Supported Functionsn/a Examples
Original EstimateOnly 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. SyntaxoriginalEstimate Alias: timeOriginalEstimate Field TypeDURATION Supported Operators
Supported Functionsn/a Examples
ParentOnly 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. Syntaxparent Field TypeISSUE Supported Operators
Supported Functionsn/a Examples
PrioritySearch for issues with a particular Priority. You can search by Priority name or Priority ID (i.e. the number that JIRA automatically allocates to a Priority).
Note: this field supports auto-complete. Syntaxpriority Field TypePRIORITY Supported Operators
Supported Functionsn/a Examples
ProjectSearch 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. Syntaxproject Field TypePROJECT Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, project supports: Examples
Remaining EstimateOnly 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. SyntaxremainingEstimate Alias: timeEstimate Field TypeDURATION Supported Operators
Supported Functionsn/a Examples
ReporterSearch 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. Syntaxreporter Field TypeUSER Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: When used with the EQUALS and NOT_EQUALS operators, this field supports: Examples
ResolutionSearch for issues that have a particular Resolution You can search by Resolution name or Resolution ID (i.e. the number that JIRA automatically allocates to a Resolution).
Note: this field supports auto-complete. Syntaxresolution Field TypeRESOLUTION Supported Operators
Supported Functionsn/a Examples
ResolvedSearch 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. Use one of the following formats: "yyyy/MM/dd HH:mm" 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. Syntaxresolved Alias: resolutionDate Field TypeDATE Supported Operators
Supported FunctionsWhen used with the EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_EQUALS, LESS_THAN or LESS_THAN_EQUALS operators, resolved supports:
Examples
StatusSearch 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).
Note: this field supports auto-complete. Syntaxstatus Field TypeSTATUS Supported Operators
Supported Functionsn/a Examples
SummarySearch for issues where the Summary contains particular text. JIRA text-search syntax can be used. Note: this field does not support auto-complete. Syntaxsummary Field TypeTEXT Supported Operators
Supported Functionsn/a Examples
TextThis 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 "!~"). Syntaxtext Field TypeTEXT Supported Operators
Supported Functionsn/a Examples
TypeSearch for issues that have a particular Issue Type. You can search by Issue Type name or Issue Type ID (i.e. the number that JIRA automatically allocates to an Issue Type).
Note: this field supports auto-complete. Syntaxtype Alias: issueType Field TypeISSUE_TYPE Supported Operators
Supported Functionsn/a Examples
Time SpentOnly 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. SyntaxtimeSpent Field TypeDURATION Supported Operators
Supported Functionsn/a Examples
UpdatedSearch 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. Use one of the following formats: "yyyy/MM/dd HH:mm" 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. Syntaxupdated Alias: updatedDate Field TypeDATE Supported Operators
Supported FunctionsWhen used with the EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_EQUALS, LESS_THAN or LESS_THAN_EQUALS operators, this field supports:
Examples
VoterSearch 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. Syntaxvoter Field TypeUSER Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: When used with the EQUALS and NOT_EQUALS operators, this field supports: Examples
VotesSearch for issues with a specified number of votes. Note: this field does not support auto-complete. Syntaxvotes Field TypeNUMBER Supported Operators
Supported Functionsn/a Examples
WatcherSearch 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. Syntaxvoter Field TypeUSER Supported Operators
Supported FunctionsWhen used with the IN and NOT_IN operators, this field supports: When used with the EQUALS and NOT_EQUALS operators, this field supports: Examples
Work RatioOnly 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. SyntaxworkRatio Field TypeNUMBER Supported Operators
Supported Functionsn/a Examples
Functions Reference
cascadeOption()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. SyntaxcascadeOption(parentOption) or cascadeOption(parentOption,childOption) Supported Fields
Supported Operators
Examples
componentsLeadByUser()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. SyntaxcomponentsLeadByUser() or componentsLeadByUser(username) Supported FieldsSupported Operators
Examples
currentLogin()Perform searches based on the time at which the current user's session began. See also lastLogin. SyntaxcurrentLogin() Supported FieldsSupported Operators
Examples
currentUser()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. SyntaxcurrentUser() Supported FieldsSupported Operators
Examples
earliestUnreleasedVersion()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. SyntaxearliestUnreleasedVersion(project) Supported Fields
Supported Operators
Examples
endOfDay()Perform searches based on the end of the current day. See also endOfWeek, endOfMonth and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear. SyntaxendOfDay() endOfDay("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
endOfMonth()Perform searches based on the end of the current month. See also endOfDay, endOfWeek and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear. SyntaxendOfMonth() endOfMonth("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
endOfWeek()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. SyntaxendOfWeek() endOfWeek("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
endOfYear()Perform searches based on the end of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear. startOfYear() startOfYear("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
issueHistory()Find issues that you have recently viewed, i.e. issues that are in the 'Recent Issues' section of the 'Issues' drop-down menu. Note:
SyntaxissueHistory() Supported FieldsSupported Operators
Examples
lastLogin()Perform searches based on the time at which the current user's previous session began. See also currentLogin. SyntaxcurrentLogin() Supported FieldsSupported Operators
Examples
latestReleasedVersion()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. SyntaxlatestReleasedVersion(project) Supported Fields
Supported Operators
Examples
linkedIssues()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. SyntaxlinkedIssues(issueKey) or linkedIssues(issueKey,linkType) Supported FieldsSupported Operators
Examples
membersOf()Perform searches based on the members of a particular group. SyntaxmembersOf(Group) Supported FieldsSupported Operators
Examples
now()Perform searches based on the current time. Syntaxnow() Supported FieldsSupported Operators
Examples
projectsLeadByUser()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. SyntaxprojectsLeadByUser() or projectsLeadByUser(username) Supported FieldsSupported Operators
Examples
projectsWhereUserHasPermission()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 Also note that this function is only available if you are logged in to JIRA. SyntaxprojectsWhereUserHasPermission(permission) For the permission parameter you can specify any of the following:
Supported FieldsSupported Operators
Examples
projectsWhereUserHasRole()Find issues in projects where you have a specific role. Note that this function is only available if you are logged in to JIRA. SyntaxprojectsWhereUserHasRole(rolename) Supported FieldsSupported Operators
Examples
releasedVersions()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(). SyntaxreleasedVersions() or releasedVersions(project) Supported Fields
Supported Operators
Examples
standardIssueTypes()Perform searches based on "standard" Issue Types, that is, search for issues which are not sub-tasks. See also subtaskIssueTypes(). SyntaxstandardIssueTypes() Supported FieldsSupported Operators
Examples
startOfDay()Perform searches based on the start of the current day. See also startOfWeek, startOfMonth and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear. SyntaxstartOfDay() startOfDay("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
startOfMonth()Perform searches based on the start of the current month. See also startOfDay, startOfWeek and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear. SyntaxstartOfMonth() startOfMonth("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
startOfWeek()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. SyntaxstartOfWeek() startOfWeek("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
startOfYear()Perform searches based on the start of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear. startOfYear() startOfYear("inc") where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)
Supported FieldsSupported Operators
Examples
subtaskIssueTypes()Perform searches based on issues which are sub-tasks. See also standardIssueTypes(). SyntaxsubtaskIssueTypes() Supported FieldsSupported Operators
Examples
unreleasedVersions()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(). SyntaxunreleasedVersions() or unreleasedVersions(project) Supported Fields
Supported Operators
Examples
votedIssues()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. SyntaxvotedIssues() Supported FieldsSupported Operators
Examples
watchedIssues()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. SyntaxwatchedIssues() Supported FieldsSupported Operators
Examples
Supported FieldsSupported Operators
Examples
Setting Precedence of OperatorsYou 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. Performing Text SearchesYou 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, which includes the following sections: Using Auto-completeAs 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.
Auto-complete suggestions are not offered for all fields. Check the fields reference to see which fields support auto-complete. If you type a space at the start of your query......JIRA will offer a list of all available fields, e.g.: If you type one or more characters......JIRA will offer a list of matching fields, e.g.: If you type a field then a space......JIRA will offer a list of valid operators, e.g.: If you type a field, then an operator, then a space......JIRA will offer a list of valid values, e.g.: If you type a field, then an operator, then one or more characters......JIRA will offer a list of valid values (if your field supports this) and valid functions for the field/operator combination, e.g.:
Switching between 'Advanced' and 'Simple' SearchIn 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:
Reserved CharactersJQL has a list of reserved characters:
If you wish to use these characters in queries, you need to:
For example: summary ~ "\\[example\\]" Note that there is an additional list of reserved characters for Text Searches, which applies to the following fields:
Reserved WordsJQL 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",
(Note for JIRA administrators: this list is hard coded in the JqlStringSupportImpl.java file.) Note that there is an additional list of reserved words for Text Searches, which applies to the following fields:
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Mar 27, 2011 18:27 |