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. (Note that full-stops and symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)
Note that an issue's creator does not change, so you cannot search for past creators (e.g.
BEST RADIO AUTOMATION SOFTWARE 2016 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). Find issues in the component with ID 20500:.Find issues in the "Comp1" and"Comp2" components:Ĭomponent in (Comp1) and component in (Comp2).Find issues in the "Comp1" or "Comp2" component:.When used with the IN and NOT IN operators, component supports: Search for issues that have or do not have attachments. Note that full-stops and symbols are reserved characters and need to be surrounded by quote-marks. 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 ": ">") 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. Find issues with an AffectedVersion ID of 10350:.Find issues with an AffectedVersion of "Big Ted":.Note that full-stops are reserved characters and need to be surrounded by quote-marks. Find issues with an AffectedVersion of 3.14:.When used with the IN and NOT IN operators, this field supports: 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. Version IDs, however, are unique and cannot be changed. 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. 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. You can search by version name or version ID (i.e. Search for issues that are assigned to a particular affects version(s).
Note: it is not possible to compare two fields in JQL. 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. In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). 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). This page describes information about fields that are used for advanced searching.
0 kommentar(er)
