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.
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.
| VERSION |
| Yes |
| = , != , > , >= , < , <= 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 |
When used with the = and != operators, this field supports:
|
|
Used in Jira Service Management only.
Search for requests that have been approved or require approval. This can be further refined by user.
| USER |
| No |
| = |
| ~ , != , !~ , > , >= , < , <= IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
|
|
Search for issues that are assigned to a particular user. You can search by the user's full name, ID, or email address.
| USER |
| 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. |
| ~ , !~ , > , >= , < , <= |
When used with the IN and NOT IN operators, this field supports:
|
|
Search for issues that have or do not have attachments.
| ATTACHMENT |
| Yes |
| IS, IS NOT |
| =, != , ~ , !~ , > , >= , < , <= IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| None |
|
Search for issues that belong to projects in a particular category.
| CATEGORY |
| Yes |
| =, != IS, IS NOT, IN, NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| None |
|
Used in Jira Service Management only.
Search for types 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 or change gating strategies. Change requests that are "tracked-only" are just for record-keeping purposes.
| TEXT |
| Yes |
| = , != IS, IS NOT, IN, NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| None |
|
Search for issues that have a comment that contains particular text. Jira text-search syntax can be used.
| TEXT |
| No |
| ~ , !~ |
| = , != , > , >= , < , <= IS, IS NOT, IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| None |
|
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:
|
|
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).
| DATE |
| 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:
|
|
Search for issues that were created by a particular user. You can search by the user's full name, ID, or email address. Note that an issue's creator does not change, so you cannot search for past creators (e.g. WAS). See Reporter for more options.
| USER |
| Yes |
| = , != IS , IS NOT , IN , NOT IN |
| ~ , !~ , > , >= , < , <= CHANGED, WAS, WAS IN, WAS NOT, WAS NOT IN |
When used with the IN and NOT IN operators, this field supports:
|
|
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.
| Depends on the custom field's configuration 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. |
| = , != , > , >= , < , <= IS , IS NOT , IN , NOT IN |
| ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| = , != IS , IS NOT , IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| ~ , !~ IS , IS NOT |
| = , != , > , >= , < , <= IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| = , != IS , IS NOT , IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED |
| Different types of custom fields support different functions. |
| When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, LESS THAN or LESS THAN EQUALS operators, this field supports:
|
Version picker fields: When used with the IN and NOT IN operators, this field supports:
|
|
Used in Jira Service Management only.
Search for requests of a certain request type. You can search by request type name or request type description as configured in the Request Type configuration screen.
| Custom field |
| Yes |
| IN , NOT IN |
|
~ , !~ , > , >= , < , <=
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 project portal is created, the project key can be changed. The Request Type key cannot be changed once the Request Type is created.
|
| None |
|
Search for issues where the description contains particular text. Jira text-search syntax can be used.
| TEXT |
| No |
| ~ , !~ IS , IS NOT |
| = , != , > , >= , < , <= IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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 (").
| DATE |
| 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:
|
|
Search for issues where the environment contains particular text. Jira text-search syntax can be used.
| TEXT |
| No |
| ~ , !~ IS , IS NOT |
| = , != , > , >= , < , <= IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
Search for issues that belong to a particular epic in company-managed projects. 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).
To search for issues that belong to a particular epic in team-managed projects, use parent.
| Epic Link Relationship |
| 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:
|
|
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:
| Filter |
| Yes |
| = , != IN , NOT IN |
| ~ , !~ , > , >= , < , <= IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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.
| VERSION |
| 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. |
| ~ , !~ |
When used with the = and != operators, this field supports:
|
|
Search for issues with a particular issue key or issue ID (i.e. the number that Jira automatically allocates to an issue).
| ISSUE |
| No |
| = , != , > , >= , < , <= IN, NOT IN |
| ~ , !~ IS, IS NOT, WAS NOT, WAS NOT IN, CHANGED |
When used with the IN or NOT IN operators, issueKey supports:
|
|
Searches for issues linked or not linked to an issue. You can restrict the search to links of a particular type.
| issueLink, issueLink["link type"], or issueLinkType, where link type or LinkType is a variable you replace with the issue link type (blocks, duplicates, or is blocked by, for example). |
| Yes |
| = , != IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED , IS , IS NOT |
| None |
|
Find issues:
|
Search for issues that have a particular link type, like blocks 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! For example, 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. For more info, see Customizing cards.
| Yes |
| = , != IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED , IS , IS NOT |
| None |
|
Find issues:
|
Jira issue link types have the following properties:
For example, a link type could have the following properties:
When searching issueLinkType, Jira searches all three properties. This can mean you're unable to isolate issues with a specific inward or outward description if the link type's name and either of the descriptions are the same. This is the case for the default "Blocks" link type, where the name and outward description are "blocks".
If you need to be able to search specifically for issues with an outward description of "blocks", for example, a Jira administrator must change the name of the link type to something else. If you're a Jira admin, take a look at Configuring issue linking for more info.
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.
| LABEL |
| 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 |
| None |
|
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).
| DATE |
| 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:
|
|
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.
| SECURITY LEVEL |
| Yes |
| = , != IS , IS NOT, IN , NOT IN |
| > , >= , < , <= , ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
Used in Jira Service Management only.
Search for all requests shared with an organization. Requests that were kept private won't be returned.
| USER |
| Yes |
| = , != IN, NOT IN |
| Search for all requests shared with the organization Atlassian: |
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.
| DURATION |
| No |
| = , != , > , >= , < , <= IS , IS NOT, IN , NOT IN |
| ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
Search for all subtasks of a particular issue in company-managed projects or subtasks of a particular epic in team-managed projects. You can search by issue key or by issue ID (i.e. the number that Jira automatically allocates to an Issue).
| ISSUE |
| No |
| = , != IN , NOT IN |
| > , >= , < , <= , ~ , !~ IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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 , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| ~ , !~ |
| None |
|
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 |
| = , != IS , IS NOT, IN , NOT IN |
| > , >= , < , <= , ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
When used with the IN and NOT IN operators, project supports:
|
|
Search for issues that belong to a particular type of project, either:
Results depend on your permission level. You will only see results for products you have access to. Learn more about product access.
| projectType |
| Yes |
| =, != IN, NOT IN |
| >, >=, <, <=, ~, !~ IS, IS NOT, WAS, WAS NOT, WAS NOT IN, CHANGED |
| None |
| Find all issues in a software project: projectType = ”software” Find all issues in either a software project or a service project: projectType = ”software” OR projectType = ”service_desk” Find all issues that aren’t in a software project: projectType != ”software” |
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.
| DURATION |
| No |
| = , != , > , >= , < , <= IS , IS NOT, IN , NOT IN |
| ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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.
| USER |
| 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:
|
|
Used in Jira Service Management only.
Search for requests by the channel that they were created by. For example, you could search for all requests that were emailed to the service project, or all requests that were sent from a customer portal.
| TEXT |
| 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:
|
|
Used in Jira Service Management only.
Search for requests 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. Search results are 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).
| DATE |
| Yes |
| = , != , > , >= , < , <= 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:
|
|
The resolution field doesn't exist in Jira Service Management team-managed projects. This means you can't search for issues in Jira Service Management team-managed projects with the resolution field. Instead, you can use the statusCategory field (an issue is resolved when statusCategory = Done).
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 |
| = , != , > , >= , < , <= IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| ~ , !~ |
| None |
|
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).
| DATE |
| 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:
|
|
Used in Jira Service Management only.
Search and sort through your requests to ensure that you're hitting your SLA goals. You can search for requests whose SLAs are in a certain state of completion, or that have a certain amount of time on their SLA clock.
| Time to first response <your custom SLA name> |
| SLA |
| No |
| = , !=, > , >= , < , <= |
| ~ , !~ IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
|
|
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).
| NUMBER |
| Yes |
| = , != IS , IS NOT, IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
|
|
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:
| STATUS |
| Yes |
| = , != IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| ~ , !~ , > , >= , < , <= |
| None |
|
Search for issues where the summary contains specific text. Jira text-search syntax can be used.
| TEXT |
| No |
| ~ , !~ IS , IS NOT |
| = , != , > , >= , < , <= IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
This is a master-field that allows you to search all text fields for issues, like:
Notes:
| TEXT |
| No |
| ~ |
| !~, = , != , > , >= , < , <= IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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.
| DURATION |
| No |
| = , != , > , >= , < , <= IS , IS NOT , IN , NOT IN |
| ~ , !~ WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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.
| ISSUE_TYPE |
| Yes |
| = , != IS , IS NOT , IN , NOT IN |
| ~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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).
| DATE |
| 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:
|
|
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.
| USER |
| 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:
|
|
Search for issues with a specified number of votes.
| NUMBER |
| No |
| = , != , > , >= , < , <= IN , NOT IN |
| ~ , !~ IS , IS NOT , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED |
| None |
|
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.
| USER |
| 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:
|
|
Search for issues with a specified number of watchers.
| NUMBER |
| No |
| = , != , |