Advanced searching - fields reference
来源:互联网 发布:女生喜欢大的吗 知乎 编辑:程序博客网 时间:2024/05/22 06:49
Advanced searching - fields reference
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 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.Note, it is not possible to compare two fields in JQL.
Affected version
Search for issues that are assigned to a particular affects version(s). You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).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.
affectedVersion
= , != , > , >= , < , <=
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.~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
- releasedVersions()
- latestReleasedVersion()
- unreleasedVersions()
- earliestUnreleasedVersion()
- Find issues with an AffectedVersion of 3.14:
affectedVersion = "3.14"
Note that full-stops are reserved characters and 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 page
List of Fields:
Assignee
Search for issues that are assigned to a particular user. You can search by the user's full name, ID, or email address.
assignee
Yes
= , !=
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.
~ , !~ , > , >= , < , <=
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
Find issues that are assigned to John Smith:
assignee = "John Smith"
or
assignee = jsmithFind issues that are currently assigned, or were previously assigned, to John Smith:
assignee WAS "John Smith"
or
assignee WAS jsmithFind 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 and need to be surrounded by quote-marks.
^ top of page
Attachments
Search for issues that have or do not have attachments.
attachments
IS, IS NOT
=, != , ~ , !~ , > , >= , < , <=
IN, NOT IN,WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Search for issues that have attachments:
attachments IS NOT EMPTY
Search for issues that do not have attachments:
attachments IS EMPTY
^ top of page
Category
Search for issues that belong to projects in a particular category.
category
=, !=
IS, IS NOT, IN, NOT IN
~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Find issues that belong to projects in the "Alphabet Projects" Category:
category = "Alphabet Projects"
^ top of page
Comment
Search for issues that have a comment that contains particular text. JIRA text-search syntax can be used.
comment
No
~ , !~
= , != , > , >= , < , <=
IS, IS NOT, IN, NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
- 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 page
Component
Search for issues that belong to a particular component(s) of a project. You can search by component name or component ID (i.e. the number that JIRA automatically allocates to a component).
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.
component
Yes
= , !=
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:
- componentsLeadByUser()
- 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 page
Created
Search for issues that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).
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).
created
createdDate
No
= , != ,
IS , IS NOT , IN , NOT IN > , >= , < , <=
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN orLESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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 page
Creator
Search for issues that were created by a particular user. You can search by the user's full name, ID, or email address.
creator
Yes
= , !=
IS , IS NOT , IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN
~ , !~ , > , >= , < , <=
CHANGED
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- Search for issues that were created by Jill Jones:
creator =
"Jill Jones"
or
creator = "jjones" - Search for issues that were created by the user with email address "bob@mycompany.com":
creator =
"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 page
Custom field
Only applicable if your JIRA administrator has created one or more custom fields.
Search for issues where a particular custom field has a particular value. You can search by custom field name or custom field ID (i.e. the number that JIRA automatically allocates to an custom field).
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.
CustomFieldName
cf[CustomFieldID]
Note, JIRA text-search syntax can be used with custom fields of type 'Text'.
Yes, for custom fields of type picker, group picker, select, checkbox and radio button fields
Different types of custom field support different operators.
number and date fields
= , != , > , >= , < . <=
IS , IS NOT , IN , NOT IN
number and date fields
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
picker, select, checkbox
and radio button fields
= , !=
IS , IS NOT , IN , NOT IN
picker, select, checkbox
and radio button fields
~ , !~ ,> , >= , < . <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
text fields
~ , !~
IS , IS NOT
text fields
= , != , > , >= , < . <=
IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Different types of custom fields support different 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:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
version picker fields
- releasedVersions()
- latestReleasedVersion()
- unreleasedVersions()
- earliestUnreleasedVersion()
- 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 page
Customer Request Type
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.
"Customer Request Type"
Yes
= , !=
IN , NOT IN
> , >= , < , <= ~ , !~ ,
IS , IS NOT,
CHANGEDWAS, WAS IN, WAS NOT, WAS NOT IN
,
None
- Find issues where Customer Request Type is Request a new account in projects that the user has access to:
"Customer Request Type" =
"Request a new account"
- Find issues where the Customer Request Type is Request a new account inSimpleDesk project, where the right operand is a selected Lucene value from the auto-complete suggestion list.
"Customer Request Type" =
"sd/system-access"
Find issues where Customer Request Type is either Request a new account orGet IT Help.
"Customer Request Type" IN (
"Request a new account", "Get IT Help")
^ top of page
Description
Search for issues where the description contains particular text. JIRA text-search syntax can be used.
description
No
~ , !~
IS , IS NOT
= , !=
, > , >= , < , <=
IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN
,
CHANGED
None
- 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 page
Due
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 ("
).
due
dueDate
No
= , !=
, > , >= , < , <=
IS , IS NOT , IN , NOT IN
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
,
CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS,
LESS THAN or LESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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 page
Environment
Search for issues where the environment contains particular text. JIRA text-search syntax can be used.
environment
No
~ , !~
IS , IS NOT
= , !=
, > , >= , < , <=
IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN
,
CHANGED
None
- 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 page
Epic link
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).
"epic link"
No
= , !=
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:
- issueHistory()
- linkedIssues()
- votedIssues()
- watchedIssues()
- Find issues that belong to epic "Jupiter", where "Jupiter has the issue key ANERDS-31:
"epic link"
= ANERDS-
31
or"epic link"
= Jupiter
^ top of page
Filter
You can use a saved filter to narrow your search. You can search by filter name or filter ID (i.e. the number that JIRA automatically allocates to a saved filter).
Note:
- 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.
- An unnamed link statement in your typed query will override an ORDER BY statement in the saved filter.
- You cannot run or save a filter that would cause an infinite loop (i.e. you cannot reference a saved filter if it eventually references your current filter).
filter
request , savedFilter , searchRequest
Yes
= , !=
IN , NOT IN
~ , !~
, > , >= , < , <=
IS , IS NOT,
WAS, WAS IN, WAS NOT, WAS NOT IN
,
CHANGED
None
- 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
orfilter =
12000
and assignee = jsmith
^ top of page
Fix version
Search for issues that are assigned to a particular fix version. You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).
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.
fixVersion
Yes
= , !=
, > , >= , < , <=
IS , IS NOT,
, CHANGED
WAS, WAS IN, WAS NOT, WAS NOT ININ , 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.
~ , !~
When used with the IN and NOT IN operators, this field supports:
- releasedVersions()
- latestReleasedVersion()
- unreleasedVersions()
- earliestUnreleasedVersion()
- 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 page
Issue key
Search for issues with a particular issue key or issue ID (i.e. the number that JIRA automatically allocates to an issue).
issueKey
id , issue , key
No
= , !=
, > , >= , < , <=
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:
- issueHistory()
- linkedIssues()
- votedIssues()
- watchedIssues()
- Find the issue with key "ABC-123":
issueKey = ABC-
123
^ top of page
Labels
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.
labels
Yes
= ,
!=,
IS, IS NOT, IN, NOT IN
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.
~ , !~ , ,> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
- Find issues with an existing label:
labels = "x"
- Find issues without a specified label, including issues without a label:
labels not in ("x") or labels is EMPTY
Last viewed
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).
lastViewed
No
= , !=
, > , >= , < , <=
IS , IS NOT, IN , NOT IN
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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 page
Level
Only available if issue level security has been enabled by your JIRA administrator.
Search for issues with a particular security level. You can search by issue 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.
level
Yes
= , !=
IS , IS NOT, IN , NOT IN
> , >= , < , <= ,
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
None
- 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 page
Original estimate
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues where the original estimate is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.
originalEstimate
timeOriginalEstimate
No
= , !=
, > , >= , < , <=
IS , IS NOT, IN , NOT IN
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
None
- 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 page
Parent
Only available if sub-tasks have been enabled by your JIRA administrator.
Search for all sub-tasks of a particular issue. You can search by issue key or by issue ID (i.e. the number that JIRA automatically allocates to an Issue).
parent
No
= , !=
IN , NOT IN
> , >= , < , <= ,
~ , !~
IS , IS NOT,
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
None
- Find issues that are sub-tasks of issue TEST-1234:
parent = TEST-
1234
^ top of page
Priority
Search for issues with a particular priority. You can search by priority name or priority ID (i.e. the number that JIRA automatically allocates to a priority).
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.
priority
Yes
= , != ,
> , >= , < , <=
IS , IS NOT,
IN , NOT IN ,
, CHANGED WAS, WAS IN, WAS NOT, WAS NOT IN
~ , !~
None
- Find issues with a priority of "High":
priority = High
- Find issues with a priority ID of 10000:
priority =
10000
^ top of page
Project
Search for issues that belong to a particular project. You can search by project name, by project key or by project ID (i.e. the number that JIRA automatically allocates to a project). 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.
project
Yes
= , !=
IN , NOT IN IS , IS NOT,
> , >= , < , <= ,
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
When used with the IN and NOT IN operators, project
supports:
- projectsLeadByUser()
- projectsWhereUserHasPermission()
- projectsWhereUserHasRole()
- 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 page
Remaining estimate
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues where the remaining estimate is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.
remainingEstimate
timeEstimate
No
= , != ,
> , >= , < , <=
IN , NOT IN IS , IS NOT,
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN
, CHANGED
None
- Find issues with a remaining estimate of more than 4 hours:
remainingEstimate > 4h
^ top of page
Reporter
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.
reporter
Yes
= , !=
IN , NOT IN , IS , IS NOT,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
~ , !~ ,
> , >= , < , <=
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- Search for issues that were reported by Jill Jones:
reporter =
"Jill Jones"
or
reporter =
jjones
- Search for issues that were reported by the user with email address "bob@mycompany.com":
reporter =
"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 page
Resolution
Search for issues that have a particular resolution. You can search by resolution name or resolution ID (i.e. the number that JIRA automatically allocates to a resolution).
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.
resolution
Yes
= , != ,
> , >= , < , <=
IN , NOT IN , IS , IS NOT,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
~ , !~
None
- 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 page
Resolved
Search for issues that were resolved on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).
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).
resolved
resolutionDate
No
= , != ,
> , >= , < , <=
IN , NOT IN IS , IS NOT,
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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 page
Sprint
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).
sprint
Yes
= , !=
IN , NOT IN IS , IS NOT,
~ , !~ ,
> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
- openSprints()
- closedSprints()
- futureSprints()
- Find issues that belong to sprint 999:
sprint =
999
- Find issues that belong to sprint "February 1":
sprint =
"February 1"
- Find issues that belong to either "February 1", "February 2" or "February 3":
sprint in (
"February 1"
,
"February 2"
,
"February 3"
)
- Find issues that are assigned to a sprint:
sprint is not empty
^ top of page
Status
Search for issues that have a particular status. You can search by status name or status ID (i.e. the number that JIRA automatically allocates to a status).
Note:
- 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 that rely on that name. Status IDs, however, are unique and cannot be changed.
- The WAS, WAS NOT, WAS IN and WAS NOT IN operators can only be used with the name, not the ID.
status
Yes
= , !=
IN , NOT IN , IS , IS NOT,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
~ , !~ ,
> , >= , < , <=
None
- 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 page
Summary
Search for issues where the summary contains particular text. JIRA text-search syntax can be used.
summary
No
~ , !~
IS , IS NOT
= , != ,
> , >= , < , <=
IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- 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 page
Text
This is a "master-field" that allows you to search all text fields, i.e.:
- Summary
- Description
- Environment
- Comments
- custom fields that use the "free text searcher"; this includes custom fields of the following built-in custom field types:
- Free text field (unlimited text)
- Text field (< 255 characters)
- Read-only text field
Notes:
- The
text
master-field can only be used with the CONTAINS operator ("~
" and "!~
"). - JIRA text-search syntax can be used with these fields.
text
No
~
= , != ,!~ ,
> , >= , < , <=
IS , IS NOT ,
IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- 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 page
Time spent
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues where the time spent is set to a particular value (i.e. a number, not a date or date range). Use "w", "d", "h" and "m" to specify weeks, days, hours, or minutes.
timeSpent
No
= , !=
,
> , >= , < , <=
IN , NOT INIS , IS NOT ,
~
, !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- Find issues where the time spent is more than 5 days:
timeSpent > 5d
^ top of page
Type
Search for issues that have a particular issue type. You can search by issue type name or issue type ID (i.e. the number that JIRA automatically allocates to an issue type).
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.
type
issueType
Yes
= , !=
IN , NOT INIS , IS NOT ,
~
, !~ ,
> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- Find issues with an issue type of "Bug":
type = Bug
- Find issues with an issue typeof "Bug" or "Improvement":
issueType in (Bug,Improvement)
- Find issues with an issue type ID of 2:
issueType =
2
^ top of page
Updated
Search for issues that were last updated on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).
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).
updated
updatedDate
No
= , !=
,
> , >= , < , <=
IN , NOT INIS , IS NOT ,
~
, !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS,
LESS THAN or LESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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 page
Voter
Search for issues for which a particular user has voted. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for your own votes. See also votedIssues.
voter
Yes
= , !=
IN , NOT INIS , IS NOT ,
~
, !~ ,> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- Search for issues that you have voted for:
voter = currentUser()
- Search for issues that the user "jsmith" has voted for:
voter = "jsmith"
- Search for issues for which a member of the group "jira-administrators" has voted:
voter in membersOf("jira-administrators")
^ top of page
Votes
Search for issues with a specified number of votes.
votes
No
= , !=
,
> , >= , < , <=
IN , NOT IN
~
, !~
IS , IS NOT ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- Find all issues that have 12 or more votes:
votes >= 12
^ top of page
Watcher
Search for issues that a particular user is watching. You can search by the user's full name, ID, or email address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for issues where you are the watcher. See also watchedIssues.
watcher
Yes
= , !=
IN , NOT INIS , IS NOT ,
~
, !~ ,> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- 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-administrators":
watcher in membersOf("jira-administrators")
^ top of page
Watchers
Search for issues with a specified number of watchers.
watchers
No
= , !=
,
> , >= , < , <=
IN , NOT IN
~
, !~
IS , IS NOT ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- Find all issues that are being watched by more than 3 people:
watchers > 3
^ top of page
Work log author
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.
worklogAuthor
Yes
= , !=
IN , NOT INIS , IS NOT ,
~
, !~ ,> , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
When used with the IN and NOT IN operators, this field supports:
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
- Search for issues that you've logged work against:
worklogAuthor = currentUser()
- Search for issues that the user "jsmith" has logged work against:
worklogAuthor = "jsmith"
- Search for issues that a member of the group "jira-software-users":
worklogAuthor in membersOf("jira-software-users")
^ top of page
Work log comment
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. JIRA text-search syntax can be used.
worklogComment
No
~ , !~
= , != ,
> , >= , < , <=
IS , IS NOT ,
IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- Find issues where a comment in a work log entry contains text that matches "test sessions" (i.e. a "fuzzy" match):
comment ~
"test sessions"
- Find issues where a comment contains the exact phrase "test sessions":
summary ~
"\"test sessions\""
^ top of page
Work log date
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).
worklogDate
No
= , != ,
IS , IS NOT , IN , NOT IN > , >= , < , <=
~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN orLESS THAN EQUALS operators, this field supports:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- Find issues that have comments in work log entries created before midnight 00:00 12th December 2010:
worklogDate <
"2010/12/12"
- Find issues that have comments in work log entries created on or before 12th December 2010 (but not 13th December 2010):
worklogDate <=
"2010/12/13"
- Find issues that have comments in work log entries created on 12th December 2010 before 2:00pm:
worklogDate >
"2010/12/12"
and worklogDate <
"2010/12/12 14:00"
- Find issues that have comments in work log entries created less than one day ago:
worklogDate >
"-1d"
- Find issues that have comments in work log entries created in January 2011:
worklogDate >
"2011/01/01"
and worklogDate <
"2011/02/01"
Find issues that have comments in work log entries created on 15 January 2011:
worklogDate >
"2011/01/15"
and worklogDate <
"2011/01/16"
^ top of page
Work ratio
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues where the work ratio has a particular value. Work ratio is calculated as follows: workRatio = timeSpent / originalEstimate) x 100
workRatio
No
= , !=
,
> , >= , < , <=
IN , NOT INIS , IS NOT ,
~
, !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
None
- Find issues on which more than 75% of the original estimate has been spent:
workRatio > 75
- Advanced searching - fields reference
- Advanced searching - operators reference
- 高级属性(Advanced Fields)
- Searching BPM tasks by payload content: Flex Fields (Mapped Attributes)
- Initialize reference type static fields inline
- Kotlin Reference (九) Properties and Fields
- Searching
- searching
- 推荐:BlackBerry高级界面组件 advanced buttons, fields, and managers
- Advanced Custom Fields – 超级wordpress自定义字段插件
- C Bit Fields——C Language Reference(from msdn)
- OpenERP-限制高级搜索字段范围(Restrict the fields can be seen in "advanced search")
- Reference Pivot Fields and Pivot Items in an Excel Pivot Table, using VBA
- Advanced DBA certification guide and reference for DB2 universal database v8 for Linux, UNIX, and Wi
- Pattern Searching
- Solr Searching
- Searching Quickly
- 查找searching
- 开启Tomcat APR运行模式,优化并发性能
- memcache安全配置
- List中安全地删除对象
- CentOS 7安装Etherpad(在线协作编辑)
- 单向关系中的JoinColumn
- Advanced searching - fields reference
- 后台服务后台遇到的坑整理,以及做活动的优化经历,redis需要读写分离吗以及其他问题
- SpringMVC学习笔记(五)验证用户输入
- NGUI动态字体的制作
- [soap] -- soap简单使用
- 关于Ehcache缓存中timeToLiveSeconds和timeToIdleSeconds区别
- css代码建议
- Spring中AOP操作的相关术语
- xsl:template match的用法