本文共 42880 字,大约阅读时间需要 142 分钟。
This page describes information about fields that are used for advanced searching.A field in JQL is a word that represents a JIRA field (or a custom field that has already been defined in your JIRA applications). In a clause, a field is followed by an , which in turn is followed by one or more values (or ). 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.Note, it is not possible to compare two fields in JQL.
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).Note, it is better to search by version ID than by version name. Different projects may have versions with the same name. 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.
Syntax | affectedVersion |
---|---|
Field Type | VERSION |
Auto-complete | Yes |
Supported operators | = , != , > , >= , < , <= IS, IS NOT, IN, NOT IN 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. |
Unsupported operators | ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | When used with the IN and NOT IN operators, this field supports:
|
Examples |
|
List of Fields:
Search for issues that are assigned to a particular user. You can search by the user's full name, ID, or email address.
Syntax | assignee |
---|---|
Field Type | USER |
Auto-complete | Yes |
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. |
Unsupported operators | ~ , !~ |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
Search for issues that have or do not have attachments.
Syntax | attachments |
---|---|
Field Type | ATTACHMENT |
Auto-complete | Yes |
Supported operators | IS, IS NOT |
Unsupported operators | =, != , ~ , !~ IN, NOT IN, |
Supported functions | None |
Examples |
|
Search for issues that belong to projects in a particular category.
Syntax | category |
---|---|
Field Type | CATEGORY |
Auto-complete | Yes |
Supported operators | =, != IS, IS NOT, IN, NOT IN |
Unsupported operators | ~ , !~
|
Supported functions | None |
Examples |
|
Search for issues that have a comment that contains particular text. can be used.
Syntax | comment |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | None |
Examples |
|
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).
Note, 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 that rely on that name. Component IDs, however, are unique and cannot be changed.
Syntax | component |
---|---|
Field Type | COMPONENT |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | When used with the IN and NOT IN operators, component supports:
|
Examples |
|
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).
Use one of the following formats:
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), "d"
(days), "h"
(hours) or "m"
(minutes) to specify a date relative to the current time. The default is "m"
(minutes). Be sure to use quote-marks ("
); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Syntax | created |
---|---|
Alias | createdDate |
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
Search for issues that were created by a particular user. You can search by the user's full name, ID, or email address.
Syntax | creator |
---|---|
Field Type | USER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
CHANGED |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
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).
Note, 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 for 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 that rely on that name. Custom field IDs, however, are unique and cannot be changed.
Syntax | CustomFieldName |
---|---|
Alias | cf[CustomFieldID] |
Field Type | Depends on the custom field's configuration Note, can be used with custom fields of type 'Text'. |
Auto-complete | Yes, for custom fields of type picker, group picker, select, checkbox and radio button fields |
Supported operators | Different types of custom field support different operators. |
Supported operators: number and date fields |
|
Unsupported operators: number and date fields |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported operators: picker, select, checkbox and radio button fields | = , != IS , IS NOT , IN , NOT IN |
Unsupported operators: picker, select, checkbox and radio button fields |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported operators: text fields |
|
Unsupported operators: text fields | = , != , |
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | Different types of custom fields support different functions. |
Supported functions: date/time fields | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Supported functions: version picker fields | Version picker fields: When used with the IN and NOT IN operators, this field supports:
|
Examples |
|
Only applicable if JIRA Service Desk is installed and licensed.
Search for Issues matching a specific Customer Request Type in a service desk project. You can search for a Customer Request Type either by name or description as configured in the Request Type configuration screen.
Syntax | "Customer Request Type" |
---|---|
Field Type | Custom field |
Auto-complete | Yes |
Supported operators | = , !=
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
Search for issues where the description contains particular text. can be used.
Syntax | description |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
Search for issues that were due on, before, or after a particular date (or date range). Note that the due date relates to the date only (not to the time).
Use one of the following formats:
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks) or "d"
(days) to specify a date relative to the current date. Be sure to use quote-marks ("
).
Syntax | due |
---|---|
Alias | dueDate |
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
|
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
Search for issues where the environment contains particular text. can be used.
Syntax | environment |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
Search for issues that belong to a particular epic. The search is based on either the epic's name, issue key, or issue ID (i.e. the number that JIRA automatically allocates to an issue).
Syntax | "epic link" |
---|---|
Field Type | Epic Link Relationship |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
|
Supported functions | When used with the IN or NOT IN operators,
|
Examples |
|
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).
Note:
Syntax | filter |
---|---|
Aliases | request , savedFilter , searchRequest |
Field Type | Filter |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
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).
Note, 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.
Syntax | fixVersion |
---|---|
Field Type | VERSION |
Auto-complete | Yes |
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. |
Unsupported operators | |
Supported functions | When used with the IN and NOT IN operators, this field supports:
|
Examples |
|
Search for issues with a particular issue key or issue ID (i.e. the number that JIRA automatically allocates to an issue).
Syntax | issueKey |
---|---|
Aliases | id , issue , key |
Field Type | ISSUE |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the IN or NOT IN operators,
|
Examples |
|
Search for issues tagged with a label or list of labels. You can also search for issues without any labels to easily identify which issues need to be tagged so they show up in the relevant sprints, queues or reports.
Syntax | labels |
---|---|
Field Type | LABEL |
Auto-complete | Yes |
Supported operators |
We recommend using IS or IS NOT to search for a single label, and IN or NOT IN to search for a list of labels. |
Unsupported operators | ~ , !~ , WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | None |
Examples |
|
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).
Use one of the following formats:
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), "d"
(days), "h"
(hours) or "m"
(minutes) to specify a date relative to the current time. The default is "m"
(minutes). Be sure to use quote-marks ("
); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Syntax | lastViewed |
---|---|
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
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 level security name or issue level security ID (i.e. the number that JIRA automatically allocates to an issue level security).
Note, 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 that rely on that name. Security level IDs, however, are unique and cannot be changed.
Syntax | level |
---|---|
Field Type | SECURITY LEVEL |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
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.
Syntax | originalEstimate |
---|---|
Alias | timeOriginalEstimate |
Field Type | DURATION |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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).
Syntax | parent |
---|---|
Field Type | ISSUE |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
|
Supported functions | None |
Examples |
|
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).
Note, it is safer to search by priority 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 that rely on that name. Priority IDs, however, are unique and cannot be changed.
Syntax | priority |
---|---|
Field Type | PRIORITY |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
Search for issues that belong to a particular project. You can search by project name, by project key or by project ID (i.e. the number that JIRA automatically allocates to a project). In the rare case where there is a project whose project key is the same as another project's name, then the project key takes preference and hides results from the second project.
Syntax | project |
---|---|
Field Type | PROJECT |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
|
Supported functions | When used with the IN and NOT IN operators,
|
Examples |
|
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.
Syntax | remainingEstimate |
---|---|
Alias | timeEstimate |
Field Type | DURATION |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
Search for issues that were reported by a particular user. This may be the same as the creator, but can be distinct. You can search by the user's full name, ID, or email address.
Syntax | reporter |
---|---|
Field Type | USER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | ~ , !~ , > , >= , < , <= |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
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).
Note, it is safer to search by resolution ID than by resolution name. It is possible for your JIRA administrator to change the name of a resolution, which could break any saved filter that rely on that name. Resolution IDs, however, are unique and cannot be changed.
Syntax | resolution |
---|---|
Field Type | RESOLUTION |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | ~ , !~ |
Supported functions | None |
Examples |
|
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).
Use one of the following formats:
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), "d"
(days), "h"
(hours) or "m"
(minutes) to specify a date relative to the current time. The default is "m"
(minutes). Be sure to use quote-marks ("
); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Syntax | resolved |
---|---|
Alias | resolutionDate |
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators | ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
Search for issues that are assigned to a particular sprint. This works for active sprints and future sprints. The search is based on either the sprint name or the sprint ID (i.e. the number that JIRA automatically allocates to a sprint).
If you have multiple sprints with similar (or identical) names, you can simply search by using the sprint name — or even just part of it. The possible matches will be shown in the autocomplete drop-down, with the sprint dates shown to help you distinguish between them. (The sprint ID will also be shown, in brackets).
Syntax | sprint |
---|---|
Field Type | NUMBER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
Supported functions |
|
Examples |
|
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).
Note:
Syntax | status |
---|---|
Field Type | STATUS |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
Search for issues where the summary contains particular text. can be used.
Syntax | summary |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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 "!~
").Syntax | text |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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.
Syntax | timeSpent |
---|---|
Field Type | DURATION |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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).
Note, 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 that rely on that name. Type IDs, however, are unique and cannot be changed.
Syntax | type |
---|---|
Alias | issueType |
Field Type | ISSUE_TYPE |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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).
Use one of the following formats:
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), "d"
(days), "h"
(hours) or "m"
(minutes) to specify a date relative to the current time. The default is "m"
(minutes). Be sure to use quote-marks ("
); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Syntax | updated |
---|---|
Alias | updatedDate |
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
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 .
Syntax | voter |
---|---|
Field Type | USER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
Search for issues with a specified number of votes.
Syntax | votes |
---|---|
Field Type | NUMBER |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
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 .
Syntax | watcher |
---|---|
Field Type | USER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
Search for issues with a specified number of watchers.
Syntax | watchers |
---|---|
Field Type | NUMBER |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues a particular user has logged work against. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have "Time Tracking" permissions, unless you are searching for issues that you've logged work against.
Syntax | worklogAuthor |
---|---|
Field Type | USER |
Auto-complete | Yes |
Supported operators |
|
Unsupported operators | |
Supported functions | When used with the IN and NOT IN operators, this field supports:
When used with the EQUALS and NOT EQUALS operators, this field supports:
|
Examples |
|
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues that have a comment in a work log entry which contains particular text. can be used.
Syntax | worklogComment |
---|---|
Field Type | TEXT |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues that have comments in work log entries that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight 00:00 will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).
Use one of the following formats:
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), "d"
(days), "h"
(hours) or "m"
(minutes) to specify a date relative to the current time. The default is "m"
(minutes). Be sure to use quote-marks ("
); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Syntax | worklogDate |
---|---|
Field Type | DATE |
Auto-complete | No |
Supported operators |
|
Unsupported operators |
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
Supported functions | When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Examples |
|
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
Syntax | workRatio |
---|---|
Field Type | NUMBER |
Auto-complete | No |
Supported operators |
|
Unsupported operators | |
Supported functions | None |
Examples |
|
转载地址:http://wrcci.baihongyu.com/