Jira Core Support

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.

Syntax	affectedVersion
Field Type	VERSION
Auto-complete	Yes
Supported operators	`= , != , > , >= , < , <= , ~ , !~` `IS, IS NOT, IN, NOT IN` The comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order. For this field, the contain operators (~ and !~) find exact matches, and can be used to search through versions with a wildcard.
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: releasedVersions() latestReleasedVersion() unreleasedVersions() earliestUnreleasedVersion()
Examples	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`

Syntax	approvals
Field Type	USER
Auto-complete	No
Supported operators	`=`
Unsupported operators	`~ , != , !~ , > , >= , < , <= IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	approved() approver() myApproval() myPending() pending() pendingBy()
Examples	Find issues that require or required approval by John Smith: `approval = approver(jsmith)` Find issues that require approval by John Smith: `approval = pendingBy(jsmith)` Find issues that require approval by the current user: `approval = myPending()` Find all issues that require approval: `approval = pending()`

Syntax	assignee
Alias	cf[CustomFieldID]
Field Type	USER
Auto-complete	Yes
Supported operators	`= , !=` `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.
Unsupported operators	`~ , !~ , > , >= , < , <=`
Supported functions	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()
Examples	Find issues that are assigned to John Smith: `assignee = "John Smith"`or`assignee = jsmith` Find issues that are currently assigned, or were previously assigned, to John Smith: `assignee WAS "John Smith"` or`assignee WAS jsmith` Find issues that are assigned by the user with email address "bob@mycompany.com": `assignee = "bob@mycompany.com"` _{Note that full-stops and "@" symbols are reserved characters and need to be surrounded by quote-marks.}

Syntax	attachments
Field Type	ATTACHMENT
Auto-complete	Yes
Supported operators	`IS, IS NOT`
Unsupported operators	`=, != , ~ , !~ , > , >= , < , <=` `IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
Supported functions	None
Examples	Search for issues that have attachments: `attachments IS NOT EMPTY` Search for issues that do not have attachments: `attachments IS EMPTY`

Syntax	category
Field Type	CATEGORY
Auto-complete	Yes
Supported operators	`=, !=` `IS, IS NOT, IN, NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
Supported functions	None
Examples	Find issues that belong to projects in the "Alphabet Projects" Category: `category = "Alphabet Projects"`

Syntax	comment
Field Type	TEXT
Auto-complete	No
Supported operators	`~ , !~`
Unsupported operators	`= , != , > , >= , < , <= IS, IS NOT, IN, NOT IN,` `WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
Supported functions	None
Examples	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\""`

Syntax	component
Field Type	COMPONENT
Auto-complete	Yes
Supported operators	`= , != IS , IS NOT , IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
Supported functions	When used with the IN and NOT IN operators, component supports: componentsLeadByUser()
Examples	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`

Syntax	created
Alias	createdDate
Field Type	DATE
Auto-complete	No
Supported operators	`= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Examples	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"`

Syntax	creator
Field Type	USER
Auto-complete	Yes
Supported operators	`= , != IS , IS NOT , IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `CHANGED`
Supported functions	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()
Examples	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.)}`

Syntax	CustomFieldName
Alias	cf[CustomFieldID]
Field Type	Depends on the custom field's configuration Note, Jira text-search syntax 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	`= , != , > , >= , < . <= IS , IS NOT , IN , NOT IN`
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	`~ , !~ IS , IS NOT`
Unsupported operators: text fields	`= , != , > , >= , < . <=` `IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Supported functions: version picker fields	Version picker fields: When used with the IN and NOT IN operators, this field supports: releasedVersions() latestReleasedVersion() unreleasedVersions() earliestUnreleasedVersion()
Examples	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`

Syntax	"Customer Request Type"
Field Type	Custom field
Auto-complete	Yes
Supported operators	`= , !=` `IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED` Note that the Lucene value for Customer Request Type, is `portal-key/request-type-key` . While the portal key cannot be changed after a service desk portal is created, the project key can be changed. The Request Type key cannot be changed once the Request Type is created.
Supported functions	None
Examples	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 in SimpleDesk 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 or Get IT Help. `"Customer Request Type" IN ( "Request a new account", "Get IT Help")`

Syntax	Time to resolution `Time to first response` <`your custom SLA name`>
Field Type	SLA
Auto-complete	No
Supported operators	`= , !=, > , >= , < , <=`
Unsupported operators	`~ , !~ IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	breached() completed() elapsed() everBreached() paused() remaining() running() withinCalendarHours()
Examples	Find issues where Time to First Response was breached: `"Time to First Response" = everBreached()` Find issues where the SLA for Time to Resolution is paused due to a condition: `"Time to Resolution" = paused()` Find issues where the SLA for Time to Resolution is paused due to the SLA calendar: `"Time to Resolution" = withinCalendarHours()` Find issues that have been waiting for a response for more 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")`

Syntax	description
Field Type	TEXT
Auto-complete	No
Supported operators	`~ , !~ IS , IS NOT`
Unsupported operators	`= , != , > , >= , < , <=` `IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	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\""`

Syntax	due
Alias	dueDate
Field Type	DATE
Auto-complete	No
Supported operators	`= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Examples	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"`

Syntax	environment
Field Type	TEXT
Auto-complete	No
Supported operators	`~ , !~` `IS , IS NOT`
Unsupported operators	`= , != , > , >= , < , <=` `IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	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\""`

Syntax	"epic link"
Field Type	Epic Link Relationship
Auto-complete	Yes
Supported operators	`= , !=` `IS , IS NOT, IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	When used with the IN or NOT IN operators, `epic link` supports: issueHistory() linkedIssues() votedIssues() watchedIssues()
Examples	Find issues that belong to epic "Jupiter", where "Jupiter has the issue key ANERDS-31: `"epic link"` `= ANERDS-` `31 or "epic link" = Jupiter`

Syntax	filter
Aliases	request , savedFilter , searchRequest
Field Type	Filter
Auto-complete	Yes
Supported operators	`= , !=` `IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Search the results of the filter "My Saved Filter" (which has an ID of 12000) for issues assigned to the user jsmith: `filter = "My Saved Filter" and assignee = jsmith or filter = 12000 and assignee = jsmith`

Syntax	fixVersion
Field Type	VERSION
Auto-complete	Yes
Supported operators	`= , != , > , >= , < , <= , ~ , !~` `IS , IS NOT, IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED` The comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order. For this field, the contain operators (~ and !~) find exact matches, and can be used to search through versions with a wildcard.
Unsupported operators
Supported functions	When used with the IN and NOT IN operators, this field supports: releasedVersions() latestReleasedVersion() unreleasedVersions() earliestUnreleasedVersion()
Examples	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`

Syntax	issueKey
Aliases	id , issue , key
Field Type	ISSUE
Auto-complete	No
Supported operators	`= , != , > , >= , < , <=` `IS , IS NOT, IN , NOT IN`
Unsupported operators	`~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	When used with the IN or NOT IN operators, `issueKey` supports: issueHistory() linkedIssues() updatedBy() votedIssues() watchedIssues()
Examples	Find the issue with the key "ABC-123": `issueKey = ABC-123` Find several issues with the known keys "SCRUM-25" and "SCRUM-12" `issuekey in (SCRUM-25, SCRUM-12)`

Syntax	issueLinkType
Auto-complete	Yes
Supported operators	`= , !=` `IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED , IS , IS NOT`
Supported functions	None
Examples	Find issues with a link type of "blocks": `issueLinkType = blocks` Find issues with an issue type of "duplicates" or "is duplicated by": `issueLinkType in (duplicates,"is duplicated by")` Find issues with link types other than “clones”: `issueLinkType != clones` This query will also return issues with no links at all. Find issues that are blocker by other issues, or that don't have any blockers. `issueLinkType = "is blocked by"` `issueLinkType != "is blocked by"`

Syntax	labels
Field Type	LABEL
Auto-complete	Yes
Supported operators	`= , !=,` `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.
Unsupported operators	`~ , !~ , , > , >= , < , <=` `WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED`
Supported functions	None
Examples	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`

Syntax	lastViewed
Field Type	DATE
Auto-complete	No
Supported operators	`= , != , > , >= , < , <=` `IS , IS NOT, IN , NOT IN`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Examples	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"`

Page

Viewport

Confluence

Versions

Advanced searching - fields reference

Advanced searching

On this page

Related content

Still need help?

Affected version

Approvals

Assignee

Attachments

Category

Comment

Component

Created

Creator

Custom field

Customer Request Type

Description

Due

Environment

Epic link

Filter

Fix version

Issue key

Issue link type

Labels

Last viewed

Level

Original estimate

Parent

Priority

Project

Remaining estimate

Reporter

Request channel type

Request last activity time

Resolution

Resolved

SLA

Sprint

Status

Status category

Summary

Text

Time spent

Type

Updated

Voter

Votes

Watcher

Watchers

Work log author

Work log comment

Work log date

Work ratio

Related content

Syntax	originalEstimate
Alias	timeOriginalEstimate
Field Type	DURATION
Auto-complete	No
Supported operators	`= , != , > , >= , < , <=` `IS , IS NOT, IN , NOT IN`
Unsupported operators	`~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Find issues with an original estimate of 1 hour: `originalEstimate = 1h` Find issues with an original estimate of more than 2 days: `originalEstimate > 2d`

Syntax	remainingEstimate
Alias	timeEstimate
Field Type	DURATION
Auto-complete	No
Supported operators	`= , != ,` `> , >= , < , <=` `IS , IS NOT, IN , NOT IN`
Unsupported operators	`~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Find issues with a remaining estimate of more than 4 hours: remainingEstimate > 4h

Syntax	request-channel-type
Field Type	TEXT
Auto-complete	Yes
Supported operators	`= , !=` `IS, IS NOT, IN, NOT IN`
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: `email`: requests submitted via email `Jira`: requests created using Jira `portal`: requests created using a Service Desk portal `api`: requests created using a REST API
Examples	Find issues where the request channel was email: `request-channel-type = email` Find issues where the request channel was something other than a service desk portal: request-channel-type != portal

Syntax	request-last-activity-time
Field Type	DATE
Auto-complete	Yes
Supported operators	`= , != , > , >= , < , <=` `IS, IS NOT, IN, NOT IN`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Examples	Find all issues last acted on before 23rd May 2016: `request-last-activity-time <` `"2016/05/23"` Find all issues last acted on or before 23rd May 2016: `request-last-activity-time <= "2016/05/23"` Find all issues created on 23rd May 2016 and last acted on before 2:00pm that day:`created > "2016/05/23" AND request-last-activity-time < "2016/05/23 14:00"` Find issues last acted on less than one day ago: `request-last-activity-time >` `"-1d"` Find issues last acted on in January 2016: `request-last-activity-time >` `"2016/01/01"` `and request-last-activity-time <` `"2016/02/01"`

Syntax	statusCategory
Aliases	New, Indeterminate, Complete
Field Type	STATUS
Auto-complete	Yes
Supported operators	`= , !=,` `IN , NOT IN`
Unsupported operators	`~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Find issues with the status category "To Do": `statusCategory = "To Do"` Find issues with the status category ID `3` where `3` stands for closed issues: `statusCategory =` 3 Find all issues that are currently in progress: `statusCategory not in ("To Do", "Done")`

Syntax	timeSpent
Field Type	DURATION
Auto-complete	No
Supported operators	`= , !=` `, > , >= , < , <= IS , IS NOT , IN , NOT IN`
Unsupported operators	`~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Find issues where the time spent is more than 5 days: `timeSpent > 5d`

Syntax	worklogAuthor
Field Type	USER
Auto-complete	Yes
Supported operators	`= , !=` `IS , IS NOT , IN , NOT IN`
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: membersOf() When used with the EQUALS and NOT EQUALS operators, this field supports: currentUser()
Examples	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")`

Syntax	worklogComment
Field Type	TEXT
Auto-complete	No
Supported operators	`~ , !~`
Unsupported operators	`= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	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\""`

Syntax	worklogDate
Field Type	DATE
Auto-complete	No
Supported operators	`= , != , > , >= , < , <= IS , IS NOT , IN , NOT IN`
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: currentLogin() lastLogin() now() startOfDay() startOfWeek() startOfMonth() startOfYear() endOfDay() endOfWeek() endOfMonth() endOfYear()
Examples	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"`

Syntax	workRatio
Field Type	NUMBER
Auto-complete	No
Supported operators	`= , !=` `, > , >= , < , <= IS , IS NOT , IN , NOT IN`
Unsupported operators	`~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED`
Supported functions	None
Examples	Find issues on which more than 75% of the original estimate has been spent: `workRatio > 75`