JQL fields

2024-11-26 JQL lets you search fora value in a specific field. Each field in Jira has a corresponding JQL name. If you’ve made a custom field,you’ll be asked to

JQL lets you search fora value in a specific field. Each field in Jira has a corresponding JQL name. If you’ve made a custom field,you’ll be asked to name the field.

In a clause,a field is followed by an operator,which in turn is followed by one ormore values (or functions). The operatorcompares the value of the field with one ormore values orfunctions on the right,such that only true results are retrieved by the clause. It’s not possible to compare two fields in JQL.

affected version

Search forissues that are assigned to a particular affects version(s). You can search by version name orversion ID (i.e. the number that Jira automatically allocate to a version ) . note ,it is is is well to search by version ID than by version name . different projects is have may have version with the same name . It is is is also possible foryourJira administratorto 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	`1affectedversion`
field type	VERSION
auto – complete	Yes
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT INNote that the comparison operators (e.g. “>”) use the version order that has been set up by your project administrator,not a numeric oralphabetic order .
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	When used with the = and != operators,this field supports: When used with the IN and NOT IN operator,this field is supports support : releasedversion ( ) unreleasedversion ( )
example	find issue with an AffectedVersion of 3.14 : affectedversion = “3.14” _{note that full – stop are reserve character and need to be surround by quote – mark .} find issue with an AffectedVersion of ” Big Ted ” : affectedversion = “Big Ted” Find issues with an AffectedVersion ID of 10350: affectedversion = 10350

Approvals

Used in business projectJira Service Management only .

Search forrequests that have been approved orrequire approval. This can be further refined by user.

Syntax	`1approvals`
field type	USER
auto – complete	No
support operator	=
unsupported operator	~ ,!= ,!~ ,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	approved() approver ( ) myApproval() mypending ( ) myPendingApproval ( ) pending() pendingBy()
example	Find requests that require orrequired approval by John Smith: approval = approver(jsmith ) Find requests that require approval by John Smith: approval = pendingBy(jsmith ) Find requests that require orhave required approval by the current user: approval = mypending ( ) find all request that require approval : approval = pending()

Assignee

Search forissues that are assigned to a particular user. You can search by the user’s full name,ID,oremail address.

Syntax	`1assignee`
field type	USER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN ,WAS ,WAS IN ,WAS NOT ,WAS NOT IN ,change Note that the comparison operators (e.g. “>”) use the version order that has been set up by your project administrator,not a numeric oralphabetic order .
unsupported operator	~ ,! ~,> ,>= ,< ,<=
support function	When used with the IN and NOT IN operator,this field is supports support : When used with the EQUALS and NOT EQUALS operators,this field supports:
example	Find issues that are assigned to John Smith: assignee = “John Smith”or assignee = jsmith Find issues that are currently assigned,orwere previously assigned,to John Smith: assignee WAS jsmith Find issues that are assigned by the user with email address bob@mycompany.com :

Attachments

Search forissues that have ordo not have attachments.

Syntax	`1attachments`
field type	attachment
auto – complete	Yes
support operator	IS,IS NOT
unsupported operator	=,!= ,~ ,! ~,> ,>= ,< ,<= IN,NOT IN,WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	None
example

Syntax	`1category`
field type	CATEGORY
auto – complete	Yes
support operator	=,!= IS,IS NOT,IN,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	None
example

change gating type

Used in business project only .

Search fortypes of change gating that are used in change requests. “Tracked-only” requests are produced by integrations that stand separately from a change management process. These tools don’t respect approval orchange gating strategies. Change requests that are “tracked-only” are just forrecord-keeping purposes.

Syntax	`1change - gating - type`
field type	text
auto – complete	Yes
support operator	= ,! = IS,IS NOT,IN,NOT IN
unsupported operator	~ ,! ~, > ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	None
example

Search forissues that have a comment that contains particular text using Jira text-search syntax. More about searching syntax fortext fields.

Syntax	`1comment`
field type	text
auto – complete	No
support operator	~ ,! ~
unsupported operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS ,WAS IN ,WAS NOT ,WAS NOT IN ,change
support function	None
example	find issue where a comment contain the word ” My pc is quite old ” ( a “ term search ” 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 is is quite old\ ” “ find issue where a comment contain both the exact phrase ” My pc is quite old ” and the exact phrase “ My Mac is quite new ” : comment ~ ” \”My PC is is is quite old\ ” ” AND comment ~ “\”My Mac is quite new\””

component

search forissue that belong to a particular component(s ) of a project . You is search can search by component name orcomponent ID ( i.e. the number thatJira automatically allocates to a component).

Note,it is safer to search by component ID than by component name. different projects is have may have component with the same name ,so search by component name may return issue from multiple project . It is is is also possible foryourJira administratorto 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	`1component`
field type	COMPONENT
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	When used with the IN and NOT IN operators,component supports:
example	Find issues in the “Comp1″ or”Comp2” component: component in (Comp1,Comp2) find issue in the ” Comp1 ” and”comp2 ” component : component in (Comp1) and component in (Comp2) or component = Comp1 and component = Comp2 find issue in the component with ID 20500 : component = 20500

Created

Search forissues that were created on,before,orafter a particular date (ordate 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 follow format :

” yyyy / MM / dd HH : mm “
” yyyy – mm – dd hh : mm “
” yyyy / MM / dd “
” yyyy – MM – dd “

Or use ” w “ ( week ) , ” d “ ( day ) , ” h “ (hours) or ” m “ ( minute ) to specify a date relative to the current time . The default is is is ” m “ ( minute ) . Be sure to use quote – mark (“); if you omit the quote-marks,the number you supply will be interpreted as milliseconds after epoch (1970-1-1).

Syntax	`1created`
Alias	`1createdDate`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	When used with the EQUALS ,NOT EQUALS ,great THAN ,great THAN EQUALS ,LESS THAN orLESS THAN EQUALS operator,this field is supports support : currentlogin ( ) lastLogin ( ) now ( ) startOfDay ( ) startofweek ( ) startOfMonth ( ) startofyear ( ) endofday ( ) endofweek ( ) endofmonth ( ) endofyear ( )
example	find all issue create before 12th December 2010 : created < “2010/12/12” Find all issues created on orbefore 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 issue create 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”

Creator

Search forissues that were created by a particular user. You can search by the user’s full name,ID,oremail address. Note that an issue’s creatordoes not change,so you cannot search forpast creators (e.g. WAS). See Reporter formore options.

Syntax	`1creator`
field type	USER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= CHANGED,WAS,WAS IN,WAS NOT,WAS NOT IN
support function	When used with the IN and NOT IN operator,this field is supports support : When used with the EQUALS and NOT EQUALS operators,this field supports:
example	Search forissues that were created by Jill Jones: creator= “Jill Jones” or creator= “jjones” search forissue that were create by the user with email address : creator= “bob@mycompany.com” ( note that full – stop and ” @ ” symbol are reserve character ,so the email address need to be surround by quote – mark . )

custom field

Only applicable if yourJira administratoris created has create one ormore custom field .

Search forissues where a particular custom field has a particular value. You can search by custom field name orcustom field ID (i.e. the number that Jira automatically allocates to a custom field).

note ,it is is is safe to search by custom field ID than by custom field name . It is is is possible fora custom field to have the same name as a build – inJira system field ; in which case ,Jira will search forthe system field (not your custom field). It is also possible foryour Jira administratorto 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.

Formultiple choice and dropdown custom field ,you is search can search by both option value and option ID . However ,forperformance reason ,when usingclosedsprint ( ),futuresprint ( ),and opensprint ( ),you is search can only search by option value . Forexample ,ifclosedsprint ( ) were to return 16,the following query:

1"customField1[Dropdown]" in (12,closedsprint ( ))

would search foroption values 12 and 16 and ID12.

Syntax	`1CustomFieldName`
Alias	`1cf[customfieldid ]`
field type	Depends on the custom field’s configuration Jira text – search syntax can be used with custom field of type ‘ text ‘ .
auto – complete	Yes ,forcustom field of type picker ,group picker ,select ,checkbox and radio button field
support operator	Different types of custom field support different operators.
support operator: number and date fields	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator: number and date fields	~ ,! ~WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support operator: picker,select,checkbox and radio button field	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator: picker,select,checkbox and radio button field	~ ,! ~,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support operator: text field	~ ,! ~ IS ,IS NOT
unsupported operator: text field	= ,! =,> ,>= ,< ,<= IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support operator: url field	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator: url field	~ ,! ~,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	different types is support of custom field support different function .
support function: date / time field	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 ( )
support function: version picker fields	Version picker fields: When used with the IN and NOT IN operator,this field is supports support :
example	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

Description

Search forissues where the description contains particular text using Jira text-search syntax. More about searching syntax fortext fields.

Syntax	`1description`
field type	text
auto – complete	No
support operator	~ ,! ~ IS ,IS NOT
unsupported operator	= ,! =,> ,>= ,< ,<= IN ,NOT IN,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	Find issues where the description contains the words “Please see screenshot” (a “term search” match): description ~ “Please see screenshot” find issue where the description contain the exact phrase ” Please see screenshot ” : description ~ “\”Please see screenshot\”” Find issues where the description contains both the exact phrase “Please see screenshot” and the exact phrase “What is needed”: description ~ “\”Please see screenshot\”” AND description ~ “\”What is needed\””

Due

search forissue that were due on ,before ,orafter a particular date ( ordate range ) . note that the due date relate to the date only ( not to the time ) .

use one of the follow format :

” 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	`1due`
Alias	`1duedate`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	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 ( )
example	find all issue due before 31st December 2010 : due < “2010/12/31” Find all issues due on orbefore 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 “

Environment

Search forissues where the environment contains particular text using Jira text-search syntax. More about searching syntax fortext fields.

Syntax	`1environment`
field type	text
auto – complete	No
support operator	~ ,! ~ IS ,IS NOT
unsupported operator	= ,! =,> ,>= ,< ,<= IN ,NOT IN,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	find issue where the environment contain both the exact phrase ” Third floor” and the exact phrase “ fire escape ” : environment ~ “\”Third floor\”” AND environment ~ “\”Fire escape\”” find issue where the environment contain both the exact phrase ” Third floor” and the exact phrase “ fire escape ” : environment ~ “\”Third floor\”” AND environment ~ “\”Fire escape\””

Epic link

As of February 2024,Epic link function has been retired in favorof Parent. Existing filters that use the Epic link function still function,but you’ll need to use Parent when creating new filters.

jump down to the Parent section of this page .

filter

You can use a saved filter to narrow your search. You can search by filter name orfilter 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 fora 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 is override in your type query will override an order BY statement in the save filter .
You can’t run orsave a filter that would cause an infinite loop (i.e. you can’t reference a saved filter if it eventually references your current filter).

Syntax	`1filter`
alias	`1request ,savedfilter ,searchRequest`
field type	filter
auto – complete	Yes
support operator	= ,! = IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= IS ,IS NOT,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

Fix version

Search forissues that are assigned to a particular fix version. You can search by version name orversion ID (i.e. the number that Jira automatically allocates to a version).

It’s 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 foryour Jira administratorto 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	`1fixversion`
field type	VERSION
auto – complete	Yes
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS ,WAS IN ,WAS NOT ,WAS NOT IN ,change Note that the comparison operators (e.g. “>”) use the version order that has been set up by your project administrator,not a numeric oralphabetic order .
unsupported operator	~ ,! ~
support function	When used with the = and != operators,this field supports: When used with the IN and NOT IN operator,this field is supports support : releasedversion ( ) unreleasedversion ( )
example	find issue with a Fix Version of 3.14 or4.2 : fixversion in (“3.14”, “4.2”) ( note that full – stop are reserve character ,so they is need need to be surround by quote – mark . ) Find issues with a Fix Version of “Little Ted”: fixversion = “Little Ted” Find issues with a Fix Version ID of 10001: fixversion = 10001

Hierarchy level

filter issues according to their hierarchy level using a JQL filter. This field uses numbers that correlate to hierarchy levels. Use:

1 to filter by parent level task,such as epics. This level is defined by your Jira administrator .
0 to filter by standard level issues,such as stories ortasks
-1 to filter by subtasks

Currently,this field doesn’t support custom hierarchy levels made in Advanced Roadmaps.

Syntax	`1hierarchyLevel`
field type	Number
auto – complete	Yes
support operator	`1= ,! =,> ,>= ,< ,<= ,IN ,NOT IN`
unsupported operator	~ ,! ~,IS,IS NOT,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function
example

Issue key

Search forissues with a particular issue key orissue ID (i.e. the number that Jira automatically allocate to an issue ) .

Syntax	`1issueKey`
alias	`1id ,issue ,key`
field type	ISSUE
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IN,NOT IN
unsupported operator	~ ,! ~ IS ,IS NOT ,WAS NOT ,WAS NOT IN ,change
support function	When used with the IN or NOT IN operator, issueKey support : issueHistory() linkedissue ( ) votedissue ( ) watchedissue ( )
example

Issue link

Searches forissues linked or not linked to an issue. You can restrict the search to links of a particular type.

Syntax	issueLink,issueLink[“link type”],orissueLinktype, where link type orLinktype is a variable you replace with the issue link type (block,duplicates,oris blocked by,forexample).
auto – complete	Yes
support operator	= ,! = IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= WAS ,WAS IN ,WAS NOT ,WAS NOT IN ,CHANGED ,IS ,IS NOT
support function	None
example	find issue : with a link of any type to the issue ABC-123: issueLink = ABC-123 with link issue but not link to a specific issue :issueLink != ABC-123 linked to at least one of a list of issues: issueLink in (ABC-123,ABC-456) with link issue but not linked to any of the issues you specify: issueLink not in (ABC-123,ABC-456) that block the issue ABC-123 (link type is “block”): issueBlocks = ABC-123 orissueLink[“block”] = ABC-123 that are block by the issue ABC-123 ( link type is ” is block by ” ): issueIsBlockedBy is blocked = ABC-123 orissueLink[“is block by ” ] = ABC-123

Issue link type

Search forissues that have a particular link type,like block or is duplicated by. You can only find issues from the Jira instance you’re searching on; remote links to issues on other Jira instances won’t be included.

Use this JQL query to add colors to your issue cards! Forexample,add a red stripe to issues that have some blockers,and keep all other issues green. This will help you bring the right information to your team’s attention,at a glance. Formore info,see Customizing cards.

Syntax	`1issueLinktype`
auto – complete	Yes
support operator	= ,! = IN ,NOT IN
unsupported operator	~ ,! ~ ,> ,>= ,< ,<= WAS ,WAS IN ,WAS NOT ,WAS NOT IN ,CHANGED ,IS ,IS NOT
support function	None
example	find issue : with a link type of ” cause ” :issueLinktype = causes with a link type of ” duplicate ” or” clone ” :issueLinktype in (duplicates,clones) with link type other than “ clone ” :issueLinktype != clones that are blocked by other issues,orthat don’t have any blockers:

Jira issue link types have the following properties:

Name: The title forthe link type
Outward description : The description of how an issue affect other issue
Inward description: The description of how an issue is affected by other issues

Forexample,a link type could have the following properties:

When searchissueLinktype,Jira searches all three properties. This can mean you’re unable to isolate issues with a specific inward oroutward description if the link type’s name and either of the descriptions are the same. This is the case forthe default “Blocks” link type,where the name and outward description are “block”.

If you need to be able to search specifically forissues with an outward description of “block”,forexample,a Jira administratoris change must change the name of the link type to something else . If you is ‘re ‘re aJira admin,take a look at Configuring issue linking formore info.

Labels

Search forissues tagged with a label orlist of labels. You can also search forissues without any labels to easily identify which issues need to be tagged so they show up in the relevant sprints,queues orreports.

Syntax	`1labels`
field type	LABEL
auto – complete	Yes
support operator	= ,! =,IS,IS NOT,IN,NOT IN
unsupported operator	~ ,! ~,,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	None
example	Find issues with an existing label: labels = “x” Find issues without a specified label,including issues without a label: labels not in (“x”) orlabels is EMPTY

Last viewed

Search forissues that were last viewed on,before,orafter a particular date (ordate 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 follow format :

” yyyy / MM / dd HH : mm “
” yyyy – mm – dd hh : mm “
” yyyy / MM / dd “
” yyyy – MM – dd “

Syntax	`1lastViewed`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	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 ( )
example	find all issue last view before 12th December 2010 : lastViewed < “2010/12/12” Find all issues last viewed on orbefore 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”

Level

Only available if issue level security has been enabled by your Jira administrator .

Search forissues with a particular security level. You can search by issue level security name orissue 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 foryour Jira administratorto 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	`1level`
field type	SECURITY LEVEL
auto – complete	Yes
support operator	= ,! = IS ,IS NOT,IN ,NOT IN
unsupported operator	> ,>= ,< ,<= ,~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	Search forissues with a security level of “Really High” or”level1″: level in (“Really High”,level1) search forissue with a security level id of 123 : level = 123

Organization

Used in business project only .

Search forall requests shared with an organization. Requests that were kept private won’t be returned.

Syntax	`1organizations`
field type	USER
auto – complete	Yes
support operator	= ,! = IN,NOT IN
example	Search forall requests shared with the organization Atlassian: `1organization = " Atlassian "`

original estimate

Only available if time – tracking has been enable by yourJira administrator .

Search forissues where the original estimate is set to a particular value (i.e. a number,not a date ordate range). Use ” w “,” d “,” h ” and ” m ” to specify weeks,days,hours,orminutes.

Syntax	`1originalEstimate`
Alias	`1timeoriginalestimate`
field type	DURATION
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

Parent

Search forall child issues of a parent. Forexample,you can view all stories under an epic. This function works forboth team-managed and company-managed projects.

You is search can search by issue key orby issue ID .

Syntax	`1parent`
field type	ISSUE
auto – complete	No
support operator	= ,! = IN ,NOT IN
unsupported operator	> ,>= ,< ,<= ,~ ,! ~ IS ,IS NOT,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

Parent project

search forall child issue with a parent issue that belong to a specific project . You is search can search by project name orproject ID ( i.e. the number that Jira automatically allocate to a project ) .

Syntax	`1parentproject`
field type	project
auto – complete	No
support operator	=,!=,IN,NOT IN
unsupported operator	~,!~ WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	When used with the IN and NOT IN operator, project support :
example

Priority

search forissue with a particular priority . You is search can search by priority name orpriority ID ( i.e. the number thatJira automatically allocate to a priority ) .

Note,it is safer to search by priority ID than by priority name. It is possible foryour Jira administratorto 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	`1priority`
field type	PRIORITY
auto – complete	Yes
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
unsupported operator	~ ,! ~
support function	None
example

project

Search forissues that belong to a particular project. You can search by project name,by project key orby 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	`1project`
field type	project
auto – complete	Yes
support operator	= ,! = IS ,IS NOT,IN ,NOT IN
unsupported operator	> ,>= ,< ,<= ,~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	When used with the IN and NOT IN operator, project support :
example	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

project type

Search forissues that belong to a particular type of project,either:

“ business ” which find issue create in business project
“software” which finds issues created in Jira
“service_desk” which finds issues created in service projects

Results is depend depend on your permission level . You is see will only see result forproduct you have access to . read about product access .

Syntax	projecttype
auto – complete	Yes
support operator	=,!= IN,NOT IN
unsupported operator	>,>=,<,<=,~,!~ IS,IS NOT,WAS,WAS NOT,WAS NOT IN,CHANGED
support function	None
example	Find all issues in a software project: projecttype = ”software” Find all issues in either a software project ora service project: projecttype = ”software” OR projecttype = ”service_desk” Find all issues that aren’t in a software project: projecttype != ”software”

Remaining estimate

Only available if time – tracking has been enable by yourJira administrator .

Search forissues where the remaining estimate is set to a particular value (i.e. a number,not a date ordate range). Use ” w “,” d “,” h ” and ” m ” to specify weeks,days,hours,orminutes.

Syntax	`1remainingEstimate`
Alias	`1timeestimate`
field type	DURATION
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

Reporter

Search forissues 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,oremail address.

Syntax	`1reporter`
field type	USER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
unsupported operator	~ ,! ~,> ,>= ,< ,<=
support function	When used with the IN and NOT IN operator,this field is supports support : When used with the EQUALS and NOT EQUALS operators,this field supports:
example

request channel type

Used in business project only .

Search forrequests by the channel that they were created by. Forexample,you could search forall requests that were emailed to the service project,orall requests that were sent from a customer portal.

Syntax	`1request - channel - type`
field type	text
auto – complete	Yes
support operator	= ,! = IS,IS NOT,IN,NOT IN
unsupported operator	~ ,! ~, > ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	When used with the IN and NOT IN operator,this field is supports support : email: request send by email jira: issues created in Jira (by clicking the blue Create button) portal: requests sent from a service project portal anonymous portal: requests sent from the customer portal by a customer who was not logged in api: request send by rest API
example	Find requests where the request channel was email: request – channel – type = email find request where the request channel was something other than a service project portal : request – channel – type != portal Find requests where the request channel was sent by a CI/CD deployment tool: request – channel – type = deployment

Request last activity time

Used in business project only.

Search forrequests that were created on,before,orafter a particular date (ordate range). Note that if a time-component is not specified,midnight will be assumed. Search results are relative to your configured time zone (which is by default the Jira server ‘s time zone ) .

use one of the follow format :

” yyyy / MM / dd HH : mm “
” yyyy – mm – dd hh : mm “
” yyyy / MM / dd “
” yyyy – MM – dd “

Syntax	`1request - last - activity - time`
field type	date
auto – complete	Yes
support operator	= ,! =,> ,>= ,< ,<= IS,IS NOT,IN,NOT IN
unsupported operator	~ ,! ~WAS,WAS IN,WAS NOT,WAS NOT IN,CHANGED
support function	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 ( )
example

request type

Used in service projects only .

Search forrequests of a certain request type. You can search by request type name orrequest type description as configured in the Request type configuration screen.

Syntax	`1"Request type"`
field type	custom field
auto – complete	Yes
support operator	`1= ,! =` IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= IS ,IS NOT,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED Note that the Lucene value forRequest type,is portal-key/request-type-key. While the portal key cannot be changed after a service project portal is created,the project key can be changed. The Request type key cannot be changed once the Request type is created.
support function	None
example	Find issues where Request type is Request a new account in projects that the user has access to: ” Request type is Request ” = ” request a new account “ Find issues where the Request type is Request a new account in SimpleDesk project,where the right operand is a selected Lucene value from the auto-complete suggestion list. ” Request type ” = ” sd / system – access “ Find issues where Request type is either Request a new account orGet IT Help. “Request type” IN (“Request a new account”,”Get IT Help”)

Resolution

The resolution field doesn’t exist in service team-managed projects. This means you can’t search forissues in service team-managed projects with the resolution field. Instead,you can use the statusCategory field (an issue is resolved when statusCategory = Done).

Search forissues that have a particular resolution. You can search by resolution name orresolution 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 foryour Jira administratorto 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	`1resolution`
field type	RESOLUTION
auto – complete	Yes
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
unsupported operator	~ ,! ~
support function	None
example	Find issues with a resolution of “Can’t Reproduce” or”Won’t Fix”: resolution in (“Can’t Reproduce”,”Won’t Fix”) Find issues with a resolution ID of 5: resolution = 5 Find issues that don’t have a resolution: resolution = unresolved

Resolved

Search forissues that were resolved on,before,orafter a particular date (ordate 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 follow format :

” yyyy / MM / dd HH : mm “
” yyyy – mm – dd hh : mm “
” yyyy / MM / dd “
” yyyy – MM – dd “

Syntax	`1resolved`
Alias	`1resolutionDate`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT,IN ,NOT IN
unsupported operator	~ ,! ~WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	When used with the EQUALS ,NOT EQUALS ,great THAN ,great THAN EQUALS ,LESS THAN orLESS THAN EQUALS operator,this field is supports support : currentlogin ( ) lastLogin ( ) now ( ) startOfDay ( ) startofweek ( ) startOfMonth ( ) startofyear ( ) endofday ( ) endofweek ( ) endofmonth ( ) endofyear ( )
example	find all issue that were resolve 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 orbefore 31st December 2010: resolved <= “2011/01/01” find issue that were resolve 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 issue that were resolve in the last hour : resolved > -1h

sla

Used in service projects only.

Search and sort through your requests to ensure that you’re hitting your sla goals. You can search forrequests whose slas are in a certain state of completion,orthat have a certain amount of time on their sla clock.

Syntax	`1Time to resolution` time to first response <your custom sla name>
field type	sla
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<=
unsupported operator	~ ,! ~ IS ,IS NOT ,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	breached() complete ( ) elapsed() everBreached() pause ( ) remaining() running() withinCalendarHours()
example	Find issues where Time to First Response was breached: “Time to First Response” = everBreached() Find issues where the sla forTime to Resolution is paused due to a condition: “Time to Resolution” = pause ( ) Find issues where the sla forTime to Resolution is paused due to the sla calendar: “Time to Resolution” = withinCalendarHours() Find issues that have been waiting fora response formore than 1 hour: “Time to First Response” > elapsed(“1h”) Find issues that that will breach Time to First Response in the next two hours: “Time to First Response” < remaining(“2h”)

Sprint

search forissue that are assign to a particular sprint . This is works work foractive sprint and future sprint . The search is base on either the sprint name orthe sprint ID ( i.e. the number thatJira automatically allocates to a sprint).

If you have multiple sprints with similar (oridentical) names,you can simply search by using the sprint name — oreven 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	`1sprint`
field type	NUMBER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT,IN ,NOT IN
unsupported operator	~ ,! ~,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	opensprint ( ) closedsprint ( )
example	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 issue that are assign to a sprint : sprint is not empty

Status

Search forissues that have a particular status. You can search by status name orstatus ID (i.e. the number that Jira automatically allocates to a status).

It is ’s ’s safe to search by status ID than status name since it ’s possible foryourJira administratorto change the name of a status,which would break any saved filter that relies 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.

Syntax	`1status`
field type	STATUS
auto – complete	Yes
support operator	= ,! = IS ,IS NOT,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
unsupported operator	~ ,! ~,> ,>= ,< ,<=
support function	None
example	Find issues with a status of “Open”: status = Open find issue with a status id of 1 : status = 1 Find issues that currently have,orpreviously had,a status of “Open”: status is WAS WAS open

summary

search forissue where the summary contain specific text usingJira text-search syntax. More about searching syntax fortext fields.

Syntax	`1summary`
field type	text
auto – complete	No
support operator	~ ,! ~ IS ,IS NOT
unsupported operator	= ,! =,> ,>= ,< ,<= IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	find issue where the summary contain the word ” errorsaving file ” ( a “ term search ” match ): summary ~ “Errorsaving file” Find issues where the summary contains the exact phrase “Errorsaving file”: summary ~ “\”Errorsaving file\”” find issue where the summary contain both the exact phrase ” errorsaving file ” and the exact phrase “ create new version ” : summary ~ “\”Errorsaving file\”” AND summary ~ “\”Create new version\””

Text

This is a master-field that allows you to search all text fields forissues,such as:

search forissue that have certain text present usingJira text-search syntax. More about searching syntax fortext fields.

The text master-field can only be used with the CONTAINS operator(“~” ) .

Syntax	`1text`
field type	text
auto – complete	No
support operator	~
unsupported operator	!~,= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	Find issues where a text field contains the word “Fred”: text ~ “Fred” ortext ~ Fred Find all issues where a text field contains the words “full screen”: text ~ “full screen” Find all issues where a text field contains the exact phrase “full screen”: text ~ ” \”full screen\ ” “ Find all issues where text fields contain the exact phrase “full screen” and the exact phrase “minimize screen”: text ~ ” \”full screen\ ” ” AND text ~ “\”minimize screen\””

text field

similar totext,this is a master-field that allows you to search in most text fields (except Comments,Worklog) forissues,such as:

The textfield master-field can only be used with the CONTAINS operator(“~” ) .

Syntax	`1textfield`
field type	text
auto – complete	No
support operator	~
unsupported operator	!~,= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	Find issues where a text field contains the word “Fred”: textfield ~ “Fred” ortextfield ~ Fred Find all issues where a text field contains the words “full screen”: textfield ~ “full screen” Find all issues where a text field contains the exact phrase “full screen”: textfield ~ “\”full screen\”” Find all issues where text fields contain the exact phrase “full screen” and the exact phrase “minimize screen”: textfield ~ “\”full screen\”” AND textfield ~ “\”minimize screen\””

Time spent

Only available if time – tracking has been enable by yourJira administrator .

Search forissues where the time spent is set to a particular value (i.e. a number,not a date ordate range). Use ” w “,” d “,” h ” and ” m ” to specify weeks,days,hours,orminutes.

Syntax	`1timeSpent`
field type	DURATION
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

type

Search forissues that have a particular issue type. You can search by issue type name orissue type ID (i.e. the number that Jira automatically allocate to an issue type ) .

Note,it is safer to search by type ID than type name. It is possible foryour Jira administratorto 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	`1type`
Alias	`1issuetype`
field type	issue_type
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ ,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	find issue 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

Updated

Search forissues that were last updated on,before,orafter a particular date (ordate 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 follow format :

” yyyy / MM / dd HH : mm “
” yyyy – mm – dd hh : mm “
” yyyy / MM / dd “
” yyyy – MM – dd “

Syntax	`1updated`
Alias	`1updatedDate`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	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 ( )
example	Find issues that were last updated before 12th December 2010: updated < “2010/12/12” Find issues that were last updated on orbefore 12th December 2010: updated < “2010/12/13” find all issue that were last update 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 issue that were last update on 15 January 2011 : updated > “2011/01/15” and updated < “2011/01/16” Find issues that were last updated in January 2011: updated > “2011/01/01” and updated < “2011/02/01”

Voter

Search forissues forwhich a particular user has voted. You can search by the user’s full name,ID,oremail address. Note that you can only find issues forwhich you have the “View Voters and Watchers” permission,unless you are searching foryour own vote.

Syntax	`1voter`
field type	USER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ ,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	When used with the IN and NOT IN operators,this field supports: When used with the EQUALS and NOT EQUALS operators,this field supports:
example	Search forissues that you have voted for: voter = currentUser ( ) Search forissues that the user “jsmith” has voted for: voter = “jsmith” Search forissues forwhich a member of the group “jira-administrators” has voted: voter in membersOf(“jira – administrator ” )

vote

Search forissues with a specified number of vote.

Syntax	`1vote`
field type	NUMBER
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IN ,NOT IN
unsupported operator	~ ,! ~ IS ,IS NOT ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

Watcher

Search forissues that a particular user is watching. You can search by the user’s full name,ID,oremail address. Note that you can only find issues forwhich you have the “View Voters and Watchers” permission,unless you are searching forissues where you are the watcher. See also watchedIssues.

Syntax	`1watcher`
field type	USER
auto – complete	Yes
support operator	= ,! = IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ ,> ,>= ,< ,<= WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	When used with the IN and NOT IN operators,this field supports: When used with the EQUALS and NOT EQUALS operators,this field supports:
example	Search forissues that you are watching: watcher = currentUser() Search forissues that the user “jsmith” is watching: watcher = ” jsmith “ Search forissues that are being watched by a member of the group “jira-administrators”: watcher in membersOf(“jira – administrator ” )

Watchers

Search forissues with a specified number of watcher.

Syntax	`1watcher`
field type	NUMBER
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IN ,NOT IN
unsupported operator	~ ,! ~ IS ,IS NOT ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example

This field is only available if time tracking has been enabled by your Jira administrator,and can only support the CONTAINS operator(“~” ) .

Search forissues that have certain text present in worklog comments using Jira text-search syntax. More about searching syntax fortext fields.

Syntax	`1worklogComment`
field type	text
auto – complete	No
support operator	~
unsupported operator	!~,= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN ,WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example	Find issues where a worklog comment contains the word “Fred”: worklogComment ~ “Fred” Find all issues where a worklog comment contains the words “full screen”: worklogComment ~ “full screen” Find all issues where a worklog comment contains the exact phrase “full screen”: worklogComment ~ “\”full screen\”” Find all issues where a worklog comment contains both the exact phrase “full screen” and the exact phrase “minimize screen”: worklogComment ~ “\”full screen\”” AND worklogComment ~ “\”minimize screen\””

Worklog date

Only available if time – tracking has been enable by yourJira administrator .

Search forissues with work logged on a specific date

Syntax	`1worklogDate`
field type	date
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	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 ( )
example

Work ratio

Only available if time – tracking has been enable by yourJira administrator .

Search forissues where the work ratio has a particular value. Work ratio is calculated as follows: workRatio = timeSpent / originalEstimate) x 100

Syntax	`1workRatio`
field type	NUMBER
auto – complete	No
support operator	= ,! =,> ,>= ,< ,<= IS ,IS NOT ,IN ,NOT IN
unsupported operator	~ ,! ~ WAS,WAS IN,WAS NOT,WAS NOT IN ,CHANGED
support function	None
example