Yes, for custom fields of type picker, group picker, select, checkbox and radio button fieldsĭifferent types of custom field support different operators. Learn more about searching syntax for text fields. Jira text-search syntax can be used with custom fields of type 'Text'. Custom field IDs, however, are unique and cannot be changed.ĭepends on the custom field's configuration 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. 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). the number that Jira automatically allocates to an custom field). 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. Only applicable if your Jira administrator has created one or more custom fields. Search for issues that were created by the user with email address :Ĭreator that full-stops and symbols are reserved characters, so the email address needs to be surrounded by quote-marks.) Search for issues that were created by Jill Jones: ~, !~, >, >=, <, <= CHANGED, WAS, WAS IN, WAS NOT, WAS NOT IN Note that an issue's creator does not change, so you cannot search for past creators (e.g.
#Clone x cross reference 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. ">") 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
Search for requests that have been approved or require approval. Note that full-stops are reserved characters and need to be surrounded by quote-marks.įind issues with an AffectedVersion of "Big Ted":įind issues with an AffectedVersion ID of 10350: When used with the IN and NOT IN operators, this field supports:įind issues with an AffectedVersion of 3.14: When used with the = and != operators, this field supports: WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED =, !=, >, >=, ") use the version order that has been set up by your project administrator, not a numeric or alphabetic order.
0 kommentar(er)
