"Customer Request Type" IN ("Request a new account", "Get IT Help") "Customer Request Type" = "sd/system-access"įind issues where Customer Request Type is either Request a new account or Get IT Help. "Customer Request Type" = "Request a new account"įind 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. The Request Type key cannot be changed once the Request Type is created.įind issues where Customer Request Type is Request a new account in projects that the user has access to: While the portal key cannot be changed after a service project portal is created, the project key can be changed. Note that the Lucene value for Customer Request Type, is portal-key/request-type-key. ~, !~, >, >=, <, <= IS, IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED Version picker fields: When used with the IN and NOT IN operators, this field supports:įind issues where the value of the "Location" custom field is "New York":įind issues where the value of the custom field with ID 10003 is "New York":įind issues where the value of the "Location" custom field is "London" or "Milan" or "Paris":Ĭf in ("London", "Milan", "Paris")įind issues where the "Location" custom field has no value: LESS THAN or LESS THAN EQUALS operators, this field supports: When used with the EQUALS, NOT EQUALS, GREATER THAN, GREATER THAN EQUALS, =, !=, >, >=, , >=, , >=, , >=, <, <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGEDĭifferent types of custom fields support different functions. Yes, for custom fields of type picker, group picker, select, checkbox and radio button fieldsĭifferent types of custom field support different operators. Jira text-search syntax can be used with custom fields of type 'Text'. See Reporter for more options.ĭepends on the custom field's configuration Note that an issue's creator does not change, so you cannot search for past creators (e.g.
#Confluence and jira pricing full
Search for issues that were created by a particular user. You can search by the user's full name, ID, or email address.
Be sure to use quote-marks ( ") if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (). Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. Please note that the search results will be relative to your configured time zone (which is by default the Jira server's time zone).
Note that if a time-component is not specified, midnight will be assumed. Search for issues that were created on, before, or after a particular date (or date range). When used with the IN and NOT IN operators, component supports:įind issues in the "Comp1" or "Comp2" component:įind issues in the "Comp1" and"Comp2" components:Ĭomponent in (Comp1) and component in (Comp2)įind issues in the component with ID 20500: ~, !~, >, >=, <, <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED Search for issues that have or do not have attachments. When used with the EQUALS and NOT EQUALS operators, this field supports:įind issues that are assigned to John Smith:įind issues that are currently assigned, or were previously assigned, to John Smith:įind issues that are assigned by the user with email address = that full-stops and symbols are reserved characters and need to be surrounded by quote-marks. When used with the IN and NOT IN operators, this field supports:
.png "confluence and jira pricing")
">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order. IS, IS NOT, IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
0 kommentar(er)
