Documentation for JIRA 6.3. Not using this? See below:
(JIRA 6.2.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

The instructions on this page describe how to define and execute a search using the advanced search. You can also define and execute a search using the quick search or using basic searching.

What is an Advanced Search?

An advanced search allows you to use structured queries to search for JIRA issues. Your search results will be displayed in the Issue Navigator, where you can export them to MS Excel and many other formats. You can also save and subscribe to your advanced searches if you wish.

When you perform an advanced search, you are using the JIRA Query Language (JQL).

A simple query in JQL (also known as a 'clause') consists of a field, followed by an operator, followed by one or more values or functions. For example, the following simple query will find all issues in the "TEST" project:

(This example uses the Project field, the EQUALS operator, and the value "TEST".)

Be aware that it is not possible to compare two fields.

(info) JQL gives you some SQL-like syntax, such as the ORDER BY SQL keyword and ISNULL() SQL function (i.e. the NULL keyword in JQL). However, JQL is not a database query language. For example, JQL does not have a SELECT statement.

How to Perform an Advanced Search

  1. Choose Issues > Search for Issues. The issue navigator will be displayed.
    • If there are existing search criteria, click the New filter button to reset the search criteria.
    • If the Advanced link is showing, click it to switch to advanced searching.
  2. Type your query using the fields, operators and field values or functions.
  3. Click the Search button to run your query.

Performing Text Searches

You can use Lucene's text-searching features when performing searches on the following fields, using the CONTAINS operator:

For details, please see the page on Performing Text Searches.

Using Auto-complete

As you type your query, JIRA will recognise the context and offer a list of "auto-complete" suggestions as follows:

The list of auto-complete suggestions is displayed alphabetically and includes the first 15 matches. Note that auto-complete suggestions are not offered for function parameters.

Please note:

Icon
  • If no auto-complete suggestions are offered, your administrator may have disabled the "JQL Auto-complete" feature for your JIRA instance.
  • If you prefer not to be offered auto-complete suggestions, click the "Turn off auto-complete" link below the "Query" box.

Auto-complete suggestions are not offered for all fields. Check the fields reference to see which fields support auto-complete.

Switching between 'Advanced' and 'Simple' Search

In general, a query created using 'Simple Search' will be able to be translated to 'Advanced Search' (i.e. JQL), and back again.

However, a query created using 'Advanced Search' may not be able to be translated to 'Simple Search', particularly if:

  • the query contains an OR operator (note you can have an IN operator and it will be translated, e.g. project in (A, B))
    • i.e. even though this query: (project = JRA OR project = CONF) is equivalent to this query: (project in (JRA, CONF)), only the second query will be translated.
  • the query contains a NOT operator
  • the query contains an EMPTY operator
  • the query contains any of the comparison operators: !=, IS, IS NOT, >, >=, <, <=
  • the query specifies a field and value that is related to a project (e.g. version, component, custom fields) and the project is not explicitly included in the query (e.g. fixVersion = "4.0", without the AND project=JRA). This is especially tricky with custom fields since they can be configured on a Project/Issue Type basis. The general rule of thumb is that if the query cannot be created in the 'Simple Search' form, then if it is created using 'Advanced Search' it will not be able to be translated to 'Simple Search'.

 

Setting Precedence of Operators

You can use parentheses in complex JQL statements to enforce the precedence of operators.

For example, if you want to find all resolved issues in the SysAdmin project as well as all issues (any status, any project) currently assigned to the system administrator (bobsmith), you can use parentheses to enforce the precedence of the boolean operators in your query, i.e.:

Note that if you do not use parentheses, the statement will be evaluated left-to-right.

You can also use parentheses to group clauses, so that you can apply the NOT operator to the group.

Keywords Reference

A keyword in JQL is a word or phrase that does (or is) any of the following:

  • joins two or more clauses together to form a complex JQL query
  • alters the logic of one or more clauses
  • alters the logic of operators
  • has an explicit definition in a JQL query
  • performs a specific function that alters the results of a JQL query.

List of Keywords:

AND

Used to combine multiple clauses, allowing you to refine your search.

Note that you can use parentheses to control the order in which clauses are executed.

Examples
  • Find all open issues in the "New office" project:

  • Find all open, urgent issues that are assigned to jsmith:

  • Find all issues in a particular project that are not assigned to jsmith:

  • Find all issues for a specific release which consists of different version numbers across several projects:

  • Find all issues where neither the Reporter nor the Assignee is Jack, Jill or John:

^top of keywords | ^^top of topic

OR

Used to combine multiple clauses, allowing you to expand your search.

Note that you can use parentheses to control the order in which clauses are executed.

(Note: also see IN, which can be a more convenient way to search for multiple values of a field.)

Examples
  • Find all issues that were created by either jsmith or jbrown:

  • Find all issues that are overdue or where no due date is set:

^top of keywords | ^^top of topic

NOT

Used to negate individual clauses or a complex JQL query (a query made up of more than one clause) using parentheses, allowing you to refine your search.

(Note: also see NOT EQUALS ("!="), DOES NOT CONTAIN ("!~"), NOT IN and IS NOT.)

Examples
  • Find all issues that are assigned to any user except jsmith:

  • Find all issues that were not created by either jsmith or jbrown:

^top of keywords | ^^top of topic

EMPTY

Used to search for issues where a given field does not have a value. See also NULL.

Note that EMPTY can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues without a DueDate:

    or

^top of keywords | ^^top of topic

NULL

Used to search for issues where a given field does not have a value. See also EMPTY.

Note that NULL can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues without a DueDate:

    or

^top of keywords | ^^top of topic

ORDER BY

Used to specify the fields by whose values the search results will be sorted.

By default, the field's own sorting order will be used. You can override this by specifying ascending order ("asc") or descending order ("desc").

Examples
  • Find all issues without a DueDate, sorted by CreationDate:

  • Find all issues without a DueDate, sorted by CreationDate, then by Priority (highest to lowest):

  • Find all issues without a DueDate, sorted by CreationDate, then by Priority (lowest to highest):

Icon

Ordering by Components or Versions will list the returned issues first by Project and only then by the field's natural order (see JRA-31113).

^top of keywords | ^^top of topic


Operators Reference

An operator in JQL is one or more symbols or words which compares the value of a field on its left with one or more values (or functions) on its right, such that only true results are retrieved by the clause. Some operators may use the NOT keyword.

List of Operators:

EQUALS: =

The "=" operator is used to search for issues where the value of the specified field exactly matches the specified value. (Note: cannot be used with text fields; see the CONTAINS operator instead.)

To find issues where the value of a specified field exactly matches multiple values, use multiple "=" statements with the AND operator.

Examples
  • Find all issues that were created by jsmith:

  • Find all issues that were created by John Smith:

^top of operators | ^^top of topic

NOT EQUALS: !=

The "!=" operator is used to search for issues where the value of the specified field does not match the specified value. (Note: cannot be used with text fields; see the DOES NOT MATCH ("!~") operator instead.)

Note that typing field != value is the same as typing NOT field = value, and that field != EMPTY is the same as field IS_NOT EMPTY.

The "!=" operator will not match a field that has no value (i.e. a field that is empty). For example, component != fred will only match issues that have a component and the component is not "fred". To find issues that have a component other than "fred" or have no component, you would need to type: component != fred or component is empty.

Examples
  • Find all issues that are assigned to any user except jsmith:

    or:

  • Find all issues that are not assigned to jsmith:

  • Find all issues that were reported by me but are not assigned to me:

  • Find all issues where the Reporter or Assignee is anyone except John Smith:

  • Find all issues that are not unassigned:

    or

^top of operators | ^^top of topic

GREATER THAN: >

The ">" operator is used to search for issues where the value of the specified field is greater than the specified value. Cannot be used with text fields.

Note that the ">" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues with more than 4 votes:

  • Find all overdue issues:

  • Find all issues where priority is higher than "Normal":

^top of operators | ^^top of topic

GREATER THAN EQUALS: >=

The ">=" operator is used to search for issues where the value of the specified field is greater than or equal to the specified value. Cannot be used with text fields.

Note that the ">=" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues with 4 or more votes:

  • Find all issues due on or after 31/12/2008:

  • Find all issues created in the last five days:

^top of operators | ^^top of topic

LESS THAN: <

The "<" operator is used to search for issues where the value of the specified field is less than the specified value. Cannot be used with text fields.

Note that the "<" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues with less than 4 votes:

^top of operators | ^^top of topic

LESS THAN EQUALS: <=

The "<=" operator is used to search for issues where the value of the specified field is less than or equal to than the specified value. Cannot be used with text fields.

Note that the "<=" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual field reference.

Examples
  • Find all issues with 4 or fewer votes:

  • Find all issues that have not been updated in the past month (30 days):

^top of operators | ^^top of topic

IN

The "IN" operator is used to search for issues where the value of the specified field is one of multiple specified values. The values are specified as a comma-delimited list, surrounded by parentheses.

Using "IN" is equivalent to using multiple EQUALS (=) statements, but is shorter and more convenient. That is, typing reporter IN (tom, jane, harry) is the same as typing reporter = "tom" OR reporter = "jane" OR reporter = "harry".

Examples
  • Find all issues that were created by either jsmith or jbrown or jjones:

  • Find all issues where the Reporter or Assignee is either Jack or Jill:

  • Find all issues in version 3.14 or version 4.2:

^top of operators | ^^top of topic

NOT IN

The "NOT IN" operator is used to search for issues where the value of the specified field is not one of multiple specified values.

Using "NOT IN" is equivalent to using multiple NOT_EQUALS (!=) statements, but is shorter and more convenient. That is, typing reporter NOT IN (tom, jane, harry) is the same as typing reporter != "tom" AND reporter != "jane" AND reporter != "harry".

The "NOT IN" operator will not match a field that has no value (i.e. a field that is empty). For example, assignee not in (jack,jill) will only match issues that have an assignee and the assignee is not "jack" or "jill". To find issues that are assigned to someone other than "jack" or "jill" or are unassigned, you would need to type: assignee not in (jack,jill) or assignee is empty.

Examples
  • Find all issues where the Assignee is someone other than Jack, Jill or John:

  • Find all issues where the Assignee is not Jack, Jill or John:

  • Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D':

  • Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D', or has not been specified:

^top of operators | ^^top of topic

CONTAINS: ~

The "~" operator is used to search for issues where the value of the specified field matches the specified value (either an exact match or a "fuzzy" match — see examples below). For use with text fields only, i.e.:

Note: when using the "~" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.

Examples
  • Find all issues where the Summary contains the word "win" (or simple derivatives of that word, such as "wins"):

  • Find all issues where the Summary contains a wild-card match for the word "win":

  • Find all issues where the Summary contains the word "issue" and the word "collector":

  • Find all issues where the Summary contains the exact phrase "full screen" (see Reserved Characters for details on how to escape quote-marks and other special characters):

^top of operators | ^^top of topic

DOES NOT CONTAIN: !~

The "!~" operator is used to search for issues where the value of the specified field is not a "fuzzy" match for the specified value. For use with text fields only, i.e.:

Note: when using the "!~" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.

Examples
  • Find all issues where the Summary does not contain the word "run" (or derivatives of that word, such as "running" or "ran"):

^top of operators | ^^top of topic

IS

The "IS" operator can only be used with EMPTY or NULL. That is, it is used to search for issues where the specified field has no value.

Note that not all fields are compatible with this operator; see the individual field reference for details.

Examples
  • Find all issues that have no Fix Version:

    or

^top of operators | ^^top of topic

IS NOT

The "IS NOT" operator can only be used with EMPTY or NULL. That is, it is used to search for issues where the specified field has a value.

Note that not all fields are compatible with this operator; see the individual field reference for details.

Examples
  • Find all issues that have one or more votes:

    or

^top of operators | ^^top of topic

WAS

The "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field.

This operator has the following optional predicates:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

(Note: This operator can be used with the Assignee, Fix Version, PriorityReporter, Resolution and Status fields only.)

Examples
  • Find issues that currently have, or previously had, a status of 'In Progress':

  • Find issues that were resolved by Joe Smith before 2nd February:

  • Find issues that were resolved by Joe Smith during 2010:

^top of operators | ^^top of topic

WAS IN

The "WAS IN" operator is used to find issues that currently have, or previously had, any of multiple specified values for the specified field. The values are specified as a comma-delimited list, surrounded by parentheses.

Using "WAS IN" is equivalent to using multiple WAS statements, but is shorter and more convenient. That is, typing status WAS IN ('Resolved', 'Closed') is the same as typing status WAS "Resolved" OR status WAS "Closed".

This operator has the following optional predicates:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

(Note: This operator can be used with the Assignee, Fix Version, PriorityReporter, Resolution and Status fields only.)

Examples
  • Find all issues that currently have, or previously had, a status of 'Resolved' or 'In Progress':

^top of operators | ^^top of topic

WAS NOT IN

The "WAS NOT IN" operator is used to search for issues where the value of the specified field has never been one of multiple specified values.

Using "WAS NOT IN" is equivalent to using multiple WAS_NOT statements, but is shorter and more convenient. That is, typing status WAS NOT IN ("Resolved","In Progress") is the same as typing status WAS NOT "Resolved" AND status WAS NOT "In Progress".

This operator has the following optional predicates:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

(Note: This operator can be used with the Assignee, Fix Version, PriorityReporter, Resolution and Status fields only.)

Examples
  • Find issues that have never had a status of 'Resolved' or 'In Progress':

  • Find issues that did not have a status of 'Resolved' or 'In Progress' before 2nd February:

^top of operators | ^^top of topic

WAS NOT

The "WAS NOT" operator is used to find issues that have never had the specified value for the specified field.

This operator has the following optional predicates:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

(Note: This operator can be used with the Assignee, Fix Version, PriorityReporter, Resolution and Status fields only.)

Examples
  • Find issues that do not have, and has never had, a status of 'In Progress':

  • Find issues that did not have a status of 'In Progress' before 2nd February:

^top of operators | ^^top of topic

CHANGED

The "CHANGED" operator is used to find issues that have a value which had changed for the specified field.

This operator has the following optional predicates:

  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
  • FROM "oldvalue"
  • TO "newvalue"
Examples
  • Find issues whose assignee had changed:

  • Find issues whose status had changed from 'In Progress' back to 'Open':

  • Find issues whose priority was changed by user 'freddo' after the start and before the end of the current week.

^top of operators | ^^top of topic

Fields Reference

A field in JQL is a word that represents a JIRA field (or a custom field that has already been defined in JIRA). 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.

List of Fields:

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).

It is safer to search by version ID than by version name

Icon

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 which rely on that name. Version IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
Field Type

VERSION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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.

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:

    (Note that full-stops are reserved characters, so they need to be surrounded by quote marks.)

  • Find issues with an AffectedVersion of "Big Ted":

  • Find issues with an AffectedVersion ID of 10350:

^top of fields | ^^top of topic

Assignee

Search for issues that are assigned to a particular user. You can search by the user's Full Name, ID or Email Address.

Note: this field supports auto-complete.

Syntax
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
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:

    or

  • Find issues that are currently assigned, or were previously assigned, to John Smith:

    or

  • Find issues that are assigned by the user with email address "bob@mycompany.com":

    (Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

^top of fields | ^^top of topic

Attachments

Search for issues which have or do not have attachments. You can only use the EMPTY or IS NOT EMPTY operators for this field.

Note: this field supports auto-complete.

Syntax
Field Type

ATTACHMENT

Supported Operators

 

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

None

Examples
  • Search for issues which have attachments

  • Search for issues which do not have attachments

^top of fields | ^^top of topic

Category

Search for issues that belong to projects in a particular Category.

Note: this field supports auto-complete.

Syntax
Field Type

CATEGORY

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues that belong to projects in the "Alphabet Projects" Category:

^top of fields | ^^top of topic

Comment

Search for issues that have a Comment which contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where a Comment contains text that matches "My PC is quite old" (i.e. a "fuzzy" match:

  • Find issues where a Comment contains the exact phrase "My PC is quite old":

^top of fields | ^^top of topic

Component

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).

It is safer to search by component ID than by component name

Icon

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 which rely on that name. Component IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
Field Type

COMPONENT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

When used with the IN and NOT IN operators, component supports:

Examples
  • Find issues in the "Comp1" or "Comp2" component:

  • Find issues in the "Comp1" and"Comp2" components:

    or

  • Find issues in the component with ID 20500:

^top of fields | ^^top of topic

Created

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).

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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:

  • Find all issues created on or before 12th December 2010:

  • Find all issues created on 12th December 2010 before 2:00pm:

  • Find issues created less than one day ago:

  • Find issues created in January 2011:

  • Find issues created on 15 January 2011:

^top of fields | ^^top of topic

Creator

Search for issues that were created by a particular user.

You can search by the user's Full Name, ID or Email Address.

Note: this field supports auto-complete.

Syntax
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

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:

    or

  • Search for issues that were created by the user with email address "bob@mycompany.com":

    (Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

^top of fields | ^^top of topic

Custom Field

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).

It is safer to search by Custom Field ID than by Custom Field name

Icon

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 on 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 which rely on that name. Custom Field IDs, however, are unique and cannot be changed.

Note:

  • JIRA text-search syntax can be used with Custom Fields of type 'Text'.
  • auto-complete is supported for Custom Fields of type picker, group picker, select, check-box and radio button fields.
Syntax

Alias:

Field Type

Depends on the Custom Field's configuration

Supported Operators

Different types of Custom Fields support different operators. For the default Custom Field Types, the following operators are supported:

  • Number and date/time fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (tick)

    (tick)

    (error)

    (error)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)
  • Picker, select, check-box and radio button fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)

    (tick)

    (tick)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)
  • Text fields:

    =

    !=

    ~

    !~

    >

    >=

    <

    <=

    IS

    IS NOT

    IN

    NOT IN

    WAS

    WAS IN

    WAS NOT

    WAS NOT IN

    CHANGED

    (error)

    (error)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (tick)

    (tick)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)

    (error)
Supported Functions

Different types of Custom Fields support different functions. For the default Custom Field Types, the following functions are supported:

  • 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()
  • 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":

  • Find issues where the value of the Custom Field with ID 10003 is "New York":

  • Find issues where the value of the "Location" Custom Field is "London" or "Milan" or "Paris":

  • Find issues where the "Location" Custom Field has no value:

^top of fields | ^^top of topic

Description

Search for issues where the Description contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Description contains text that matches "Please see screenshot" (i.e. a "fuzzy" match):

  • Find issues where the Description contains the exact phrase "Please see screenshot":

^top of fields | ^^top of topic

Due

Search for issues that were due on, before or after a particular date (or date range). Note that 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 (").

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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:

  • Find all issues due on or before 31st December 2010:

  • Find all issues due tomorrow:

  • Find all issues due in January 2011:

  • Find all issues due on 15 January 2011:

^top of fields | ^^top of topic

Environment

Search for issues where the Environment contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Environment contains text that matches "Third floor" (i.e. a "fuzzy" match):

  • Find issues where the Environment contains the exact phrase "Third floor":

^top of fields | ^^top of topic

(info) Only available if you are using JIRA Agile 6.1.2 or later.

Search for issues that belong to a particular Epic in JIRA Agile. 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).

Note: this field does not support auto-complete.

Syntax
Field Type

Epic Link Relationship (this is a custom type created by JIRA Agile).

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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", which has issue key ANERDS-317:

    or

^top of fields | ^^top of topic

Filter

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).

It is safer to search by filter ID than by filter name

Icon

It is possible for a filter name to be changed, which could break a saved filter that invokes another filter by name. Filter IDs, however, are unique and cannot be changed.

Note:

  • An Advanced Searching - Fields Reference statement in your typed query will override an ORDER BY statement in the saved filter.
  • You cannot run or save a filter that would cause an infinite loop (i.e. you cannot reference a saved filter if it eventually references your current filter).
  • This field supports auto-complete.
    Syntax

    Aliases:

Field Type

FILTER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Search the results of the filter "My Saved Filter" (which has an ID of 12000) for issues assigned to the user jsmith:

    or

^top of fields | ^^top of topic

Fix Version

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).

It is safer to search by version ID than by version name

Icon

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.

Note: this field supports auto-complete.

Syntax
Field Type

VERSION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

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.

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:

    (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":

  • Find issues with a Fix Version ID of 10001:

^top of fields | ^^top of topic

Issue Key

Search for issues with a particular Issue Key or Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support auto-complete.

Syntax

Aliases:

Field Type

ISSUE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

When used with the IN or NOT IN operators, issueKey supports:

  • issueHistory()
  • linkedIssues()
  • votedIssues()
  • watchedIssues()
Examples
  • Find the issue with key "ABC-123":

^top of fields | ^^top of topic

LastViewed

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).

Note: this field does not support auto-complete.

Syntax
Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

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:

  • Find all issues last viewed on or before 12th December 2010:

  • Find all issues last viewed on 12th December 2010 before 2:00pm:

  • Find issues last viewed less than one day ago:

  • Find issues last viewed in January 2011:

  • Find issues last viewed on 15 January 2011:

^top of fields | ^^top of topic

Level

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 Security Level name or Issue Security Level ID (i.e. the number that JIRA automatically allocates to an Issue Security Level).

It is safer to search by Security Level ID than by Security Level name

Icon

It is possible for your JIRA administrator to change the name of a Security Level, which could break any saved filter which rely on that name. Security Level IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
Field Type

SECURITY LEVEL

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Search for issues with a Security Level of "Really High" or "level1":

  • Search for issues with a Security Level ID of 123:

^top of fields | ^^top of topic

Original Estimate

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.

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues with an Original Estimate of 1 hour:

  • Find issues with an Original Estimate of more than 2 days:

^top of fields | ^^top of topic

Parent

Only available if sub-tasks have been enabled by your JIRA administrator.

Search for all sub-tasks of a particular issue. You can search by Issue Key or by Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support auto-complete.

Syntax
Field Type

ISSUE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues that are sub-tasks of issue TEST-1234:

^top of fields | ^^top of topic

Priority

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).

It is safer to search by Priorty ID than by Priority name

Icon

It is possible for your JIRA administrator to change the name of a Priority, which could break any saved filter which rely on that name. Priority IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
Field Type

PRIORITY

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

Examples
  • Find issues with a Priority of "High":

  • Find issues with a Priority ID of 10000:

^top of fields | ^^top of topic

Project

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.

Note: this field supports auto-complete.

Syntax
Field Type

PROJECT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

When used with the IN and NOT IN operators, project supports:

  • projectsLeadByUser()
  • projectsWhereUserHasPermission()
  • projectsWhereUserHasRole()
Examples
  • Find issues that belong to the Project that has the name "ABC Project":

  • Find issues that belong to the Project that has the key "ABC":

  • Find issues that belong to the Project that has the ID "1234":

^top of fields | ^^top of topic

Remaining Estimate

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.

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues with a Remaining Estimate of more than 4 hours:

^top of fields | ^^top of topic

Reporter

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.

Note: this field supports auto-complete.

Syntax
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
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 reported by Jill Jones:

    or

  • Search for issues that were reported by the user with email address "bob@mycompany.com":

    (Note that full-stops and "@" symbols are reserved characters, so the email address needs to be surrounded by quote-marks.)

^top of fields | ^^top of topic

Resolution

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).

It is safer to search by Resolution ID than Resolution name

Icon

It is possible for your JIRA administrator to change the name of a Resolution, which could break any saved filter which rely on that name. Resolution IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax
Field Type

RESOLUTION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

Examples
  • Find issues with a Resolution of "Cannot Reproduce" or "Won't Fix":

  • Find issues with a Resolution ID of 5:

  • Find issues that do not have a Resolution:

^top of fields | ^^top of topic

Resolved

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).

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 that were resolved before 31st December 2010:

  • Find all issues that were resolved before 2.00pm on 31st December 2010:

  • Find all issues that were resolved on or before 31st December 2010:

  • Find issues that were resolved in January 2011:

  • Find issues that were resolved on 15 January 2011:

  • Find issues that were resolved in the last hour:

^top of fields | ^^top of topic

 

Sprint

(info) Only available if you are using JIRA Agile 6.4.

Search for issues that are assigned to a particular sprint in JIRA Agile. 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).

Syntax

(info) 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).

Field Type

Number

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

Supported Functions
  • openSprints()
  • closedSprints()
Examples
  • Find issues that belong to sprint 999:

  • Find issues that belong to sprint "February 1":

  • Find issues that belong to either "February 1", "February 2" or "February 3":

  • Find issues that are assigned to a sprint:

 

^top of fields | ^^top of topic

 

Status

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).

It is safer to search by Status ID than Status name

Icon

It is possible for your JIRA administrator to change the name of a Status, which could break any saved filter which rely on that name. Status IDs, however, are unique and cannot be changed.

Please note, though, that the WAS, WAS_NOT, WAS_IN and WAS_NOT_IN operators can only be used with the name (not the ID).

Note: this field supports auto-complete.

Syntax
Field Type

STATUS

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)
Supported Functions

n/a

Examples
  • Find issues with a Status of "Open":

  • Find issues with a Status ID of 1:

  • Find issues that currently have, or previously had, a Status of "Open":

^top of fields | ^^top of topic

Summary

Search for issues where the Summary contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

Syntax
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Summary contains text that matches "Error saving file" (i.e. a "fuzzy" match):

  • Find issues where the Summary contains the exact phrase "Error saving file":

^top of fields | ^^top of topic

Text

This is a "master-field" that allows you to search all text fields, i.e.:

Notes:

Syntax
Field Type

TEXT

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(error)

(error)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where a text field matches the word "Fred":

    or

  • Find all issues where a text field contains the exact phrase "full screen":

^top of fields | ^^top of topic

Type

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).

It is safer to search by Type ID than Type name

Icon

It is possible for your JIRA administrator to change the name of a Type, which could break any saved filter which rely on that name. Type IDs, however, are unique and cannot be changed.

Note: this field supports auto-complete.

Syntax

Alias:

Field Type

ISSUE_TYPE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues with an Issue Type of "Bug":

  • Find issues with an Issue Type of "Bug" or "Improvement":

  • Find issues with an Issue Type ID of 2:

^top of fields | ^^top of topic

Time Spent

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.

Note: this field does not support auto-complete.

Syntax
Field Type

DURATION

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues where the Time Spent is more than 5 days:

^top of fields | ^^top of topic

Updated

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).

Note: this field does not support auto-complete.

Syntax

Alias:

Field Type

DATE

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 were last updated before 12th December 2010:

  • Find issues that were last updated on or before 12th December 2010:

  • Find all issues that were last updated before 2.00pm on 31st December 2010:

  • Find issues that were last updated more than two weeks ago:

  • Find issues that were last updated on 15 January 2011:

  • Find issues that were last updated in January 2011:

^top of fields | ^^top of topic

Voter

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. See also votedIssues.

Note: this field supports auto-complete.

Syntax
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 for which you have voted:

  • Search for issues for which the user "jsmith" has voted:

  • Search for issues for which a member of the group "jira-developers" has voted:

^top of fields | ^^top of topic

Votes

Search for issues with a specified number of votes.

Note: this field does not support auto-complete.

Syntax
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find all issues that have 12 or more votes:

^top of fields | ^^top of topic

Watcher

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.

Note: this field supports auto-complete.

Syntax
Field Type

USER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
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 are watching:

  • Search for issues that the user "jsmith" is watching:

  • Search for issues that are being watched by a member of the group "jira-developers":

^top of fields | ^^top of topic

Watchers

Search for issues with a specified number of watchers.

Note: this field does not support auto-complete.

Syntax
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find all issues that are being watched by more than 3 people:

^top of fields | ^^top of topic

Work Ratio

Only available if time-tracking has been enabled by your JIRA administrator.

Search for issues where the Work Ratio has a particular value.

Work Ratio is calculated as follows: workRatio = timeSpent / originalEstimate) x 100

Note: this field does not support auto-complete.

Syntax
Field Type

NUMBER

Supported Operators

=

!=

~

!~

>

>=

<

<=

IS

IS NOT

IN

NOT IN

WAS

WAS IN

WAS NOT

WAS NOT IN

CHANGED

(tick)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(error)

(error)

(error)

(error)
Supported Functions

n/a

Examples
  • Find issues on which more than 75% of the Original Estimate has been spent:

^top of fields | ^^top of topic

 

78 Comments

  1. Hi Folks!

    I am hoping to generate results from:

    project = BOLOGNA AND status changed FROM ("x", "y", "x") to Z BEFORE "2012/09/28"

    But I get not results...and I know there are results. What I want to generate are all issues whose status was changed from x,y,z to Z before September 28, 2012.

    Help!

  2. Anonymous

    Is there a way that i can obtain the whole of Json dump and not just the first 50 (because of maxResults which is unmodifiable through query)

  3. Anonymous

    How can I specify condition of select when I need to select max 5 tasks per assagnee?

  4. Anonymous

    Hello!

    I want create filter  "resolvedDate > DueDate". Is it possible?

    I know, that "Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'."

    Are there really no way to compare these fields?

     

     

    1. Anonymous

      I am interested in a similar query "timeestimate < timespent", any pointers? Thanks.

    2. Please read the documentation (wink)

      Be aware that it is not possible to compare two fields.

       

      and have a look at the comments above.. tip: search for "compare" and you'll find it.

      Thank you

  5. Anonymous

    Hi Folks!

    I want to be able to determine - for a particular JIRA user - which JIRA items were reopened (status = 'Reopened'). One important side note is that as per our process, the assignee of a JIRA item may change over time, so the query would need to consider the assignee that was current at the time that the status change to 'Reopened' took place, therefore a simple '.... assignee = 'xxx' and status was 'Reopened' unfortunately won't work (assuming that assignee would consider the current assignee).

    Is there any way to use JQL to fulfill the following requirement:

    • List all JIRA items which had assignee = 'x' ('x' = to be specified in JQL where clause) at the point in time that the status of the issue was 'Reopened'.

    many thanks for your ideas


     

  6. Anonymous

    How can I find all issues that I (currentUser()) have modified at least 5 times? Thanks in advance.

    1. I'd do it using the Script Runner plugin to define a new JQL function

  7. Hi,

    Could someone please let me know that what date ranges are using for startofmonth or endofmonth functions? Are they include the first/last date of the month only (e.g. 1st of the month)? Or 10 days at the beginning/end of the month? Without knowing the actual date range that the function is returning make me really difficult to check the accuracy of the filter results, or explain to filter users.

    Thanks in advance.

     

  8. OffTopic but why did that mass comment deletion by Xavier Sanchez happened this morning?

    Force all discussions move to answers.atlassian.com but then why are there still some comments left?!

    I think there were some posts other users are searching / looking for so what's you intend?

    1. Yeah, the mass deletion suprised me as well.
      Also, i would suggest doing something about the e-mail on any change.

      In this case, i've received 20+ e-mails. 1 would suffice.

      1. Sorry for the emails but the comments were deleted as if they were deleted manually to make sure everything that action requires was executed properly and avoid inconsistencies.

    2. The comments, except the most recent ones (from this year), were deleted in an effort to improve CAC performance, as they made this page even bigger and it is accessed a lot. By doing so the page loads now much faster. 

  9. Unfortunately german umlaute (mutated vowel) are not found. E.g. summary ~ gärtner

    --> No matching issues found but there are these issues.

    Who knwos help? Thanks

  10. Anonymous

    How can i filter out sub issues which are in a structure to the parent story which is tagged to a Sprint

  11. Anonymous

    Older versions of JIRA showed a list of previous JQL queries that were ran. Now it only shows queries that have been saved as a filter.  Is there a way to display non-saved queries?

    1. I think it's gone. I miss it but I hear it wasn't much used?

      1. I used it... a lot.  I didn't always want to save filters when I was helping others work out their jql, but it was handy as they would invariably come back to me with a question.  Then, I could just pull it up to refresh my memory on what we were working on.  But, I suppose that I can see where others might not have used it much.

        1. Hi Paula,

          JQL history was removed in JIRA 5.2 (see upgrade notes). We have an open ticket regarding this, if you would like to add your feedback to it: https://jira.atlassian.com/browse/JRA-30607

          Kind Regards,
          Andrew

  12. How do I limit my search to 10 results?  On a Kanban board I want to apply a colour to any issue that is in the top 10 rank of the project.s

    1. Gear icon on the right of the board, Configure, Columns.

      Set the constraint to Issue Count

      Edit the min and max numbers for each column

      1. Anonymous

        I clicked the gear / Configure Columns. But now I don't see "constraint" or "Issue Count". Can you elaborate more on that?

        1. This is in a JIRA Agile (GreenHopper) board, not the Issue Navigator

  13. Anonymous

    How do we select a set of fields while filtering, like Select Clause in SQl

  14. If there a field or a means to search for a board itself in an advanced search?  I can see a board's sprint, but I can't seem to find a way to see an entire board.

  15. Anonymous

    Hello, I want to be able to retrieve a list of issues submitted for the month, afterwards, i want to get the amount of time it took prior to that issue being worked, or claimed and worked on. I see a "Time Elapsed Create to Triaged" below is the query i have created but i get no results. I am thinking that the below should give me a list of the issues created in the month of May which were triaged under 1 hour. Any help would be appreciated.

    "project = (my project)  AND created >= 2013-05-01 AND created <= 2013-06-01 AND ("Time Elapsed Create to Triaged" = "60")

     

  16. Anonymous

    Hello. How I could find a list of issues, having no linked tickets?

  17. Is there a way to query "anything that was assigned to a group within the last 7 days whether they are currently assigned or not"?
    The closest I have is:
    updated >= -1w AND assignee in membersOf("Group")

    But, I believe this returns things updated in the last week currently assigned to Group.

    1. I think what you are looking for would be:

      updated >= -1w AND assignee was in membersOf("Group")

      1. membersOf("") does not function with "was in" ... though it would be nice if it did.

  18. hello!

    i would like to know list of JIRA issues from any project i spent my time last week. is it possible to use timeSpent or other function/value for that?

    1. updated >= -7d AND timespent > 0 AND assignee was currentUser()

      1. thank you much Jeremy!

        it's better than nothing, for sure! but is it possible to get list of issues despite who was assignee and filtering by spent time reported last week my me?

        the search query you proposed does not show issues not assigned to me with my spent time reported. and vice-versa, the search shows issues assigned to me with spent time reported by anyone.

  19. The "Labels" field is not described, nor are the operations which can be applied to it.  Equals seems to work if there's only a single label, but some documentation would be nice.

    1. Worse still, adding the following to a JQL query that returns results

      returns no results.

       

       

  20. Anonymous

    Use (labels not in(productionEmergency) OR labels is EMPTY)
    JRA-24511 - JQL - When using 'NOT IN()' for custom fields and labels results should include EMPTY Resolved  

  21. Anonymous

    Hi,

    is there a function that will allow me to  filter all the issues that were created on the current date ( I mean today)? I need to create 2 filters:

    one that will display all the issues created ''today'' by a specific group

    and another one that will display all the issues which assignee changed from ''assignee name'' to assignee name'' on today?

    I know I can put the date range in the simple search, but If I can create a filter in which the ''date'' updates to the current day automatically it will be great.

    Thanks.

     

    1. This should work.  Just add your project info.

      createdDate >= startOfDay()

      assignee changed AFTER startOfDay()

  22. Anonymous

    Thanks a lot !! 

  23. Anonymous

    Hi Everyone,

    I have several Boards that includes more than 1 open and closed Sprint.

    How can I do a search for Task Complete on a Backlog of a specific Board?

    I currently tried: 

    status = "Task Complete" AND assignee in (.....) AND Sprint not in openSprints()

    However, it is pulling the information across all the boards.

    In a side note, how can I look for Task Complete that has an active "Start Testing" button?

    Is it possible to look for issue in a created but not started sprint? (I'm trying to see if I have not over allocated my resource prior to start the Sprint).

     

    Thank you!!!

     

    1. Anonymous

      I too am wondering if there is a way to search on stories that are queued up in the upcoming sprint.  Anybody out there with some insight?

       

      Thanks

  24. Hi everyone,

    I was able to create a pie chart on my dashboard to see for the openSprint() the Remaining Estimate per Team Member.

    How can I see the time logged per team member on that sprint?

    I tried with Time Spent but it accumulate the time spent on each task since the creation of the task and not in the openSprint().

    Thanks,

     

    Vince

  25. Anonymous

    Is there any way to search for a ticket that is/is-not blocked by anything?

  26. I know it is possible to check whether checkbox is checked, but is it possible to check that it is unchecked? 

  27. Regarding the example query used above of

    "parent = TEST-1234"

    We tried using this approach in our "search for issues" screen (using an issue ID of an item with subtasks), e.g. "parent = DLITE-17", and we get the error message of "An issue with key 'DLITE-17' does not exist for field 'parent'."  (We tried this with a number of issues, and got the same error every time).  Any thoughts on whether this is a bug, or potentially something to do with our configuration?  (We're on Jira 6.0 on-premise).

    1. Hello Andrew, I checked with our Support team and this does sound like a bug. Please contact them directly at https://support.atlassian.com/ for further assistance.

      Thanks,

      Susan

      1. We have a lot of tasks linked and I need to prioritize the work within those containers. It would be nice to have a filter of the issues with a single parent in the Kanban board. I have a workaround, but it's not nearly as elegant. We're on 5.2 presently but I plan to annoy the admins to upgrade.

         

  28. Hey Atlassian, I'm ok with operator precedence, but please do not remove brackets from saved jql-s. It simply takes more time to re-understand how a complex filter works. If I'd like to group something, I don't want to decode 3 months later. Thanks!

  29. It seems the JQL for the quick-filter buttons (and swimlanes) in our planning board do not take working/non-working days into account.  We have a swimlane for "all tasks due in the next 5 days" and a "due soon" quick-filter for tasks due <= 2 days.

    Tasks sneak up on us because weekend is counted even though Sat & Sun are marked as non-working days.  You can imagine pressing the button on Friday; seeing that there are no tasks due in the next 2 days. Then on Monday... Bam! lots of tasks are due.

    Is there a trick for getting this to work? Maybe "2D" is "working days" vs "2d" is days?

  30. I love opensprint()...  but how would one find subtasks in the opensprints?  parent returns issue keys, opensprints returns number??

     

    It would seem to me a bug that opensprint() does not return ALL issues (tasks, bugs, substasks, ...) associated to the currently open sprint.

    1. can't see any problem here, while

      • Sprint  in openSprints()
        returns 53 issues for me
      • Sprint  in openSprints() and issuetype in subTaskIssueTypes()
        returns 20 issues
      • Sprint  in openSprints() and issuetype in standardIssueTypes()
        returns 33 issues

      truly, only issues that are planned during sprint planning and added to the sprint plan are available here.

      Subtasks are in this list, once the parent issue is assigned to the sprint. Subtask issue types are typically not planned. Then you should revise your usage of projects, epics, tasks / stories and subtasks. Some business cases have to match the "JIRA way" of agile not the other way round (wink)

      Typically "bugs" are not planned neither automatically assigned to the current sprint automatically. They might be / should be entitled in the Sprint in closedSprints() and issuetype in (Bug) list.

      Please regard that sprint planning doesn't requisit to match your filter used for your working agile (scrum / kanban) board!

  31. Hi!

    It seems that with recent JIRA Agile versions (when Epic Link is no longer the Epic id but its name), such field cannot be anymore used for ORDER BY. This means that you cannot have Stories grouped by their containg Epic.

    Is it intentional? To my organization, it seems a huge drawback.

    Thanks, Simone

  32. Anonymous

    Similar to this, I'm looking to see a specific transition associated with a time frame.

    How many issues did Bob move from "Open" to "In Progress" today?

    1. It seems to me you want to track your staff, not the issue (sad)

      Please use https://answers.atlassian.com/ thx

    2. Try this:

      status changed by Bob from Open to "In Progress" after startOfDay()

  33. Hello ,

    I use JIRA for bug report but i want to find out that How many tickets I have participate between  specific date . Please reply me quickly, it urgent.

     

    Thanks

     

     

  34. Anonymous

    I'm trying to do something I think should be fairly simple but I can't find any documentation that indicates there is a way.  Essentially I'm creating a search for a weekly status.  So I want to have an issue for a project show up in that search if it has been updated ANY time during that week.  The issue I'm running into currently is that the "updated" part of the search only seems to be concerned with when an issue was LAST UPDATED.  Which, even though this one group has issues they are working on for this weeks updates, the issues don't appear when filtering by "updated" as they have been last updated outside of the date range of the search parameters (even though they had updates within).  How can one go about addressing this issue?

  35. Anonymous

    Hi,

    I wanted to query the JIRA API to get the details of the issues between a specific start date and end date.

    I was trying https://jira.abcd.net/rest/api/latest/search?createdDate > "14/01/28" .

    it did not work. However i change the date, it always gave the same number of records.

    Thanks

    MC

  36. Anonymous

    Sorry if this was covered in a previous note.  I'm trying to do a search for "last updated by current assignee".  The last updated field is updated whenever a Comment or anything happens.  However, I want to track only if the current assignee made the update – that way, I can flag items that have been sitting without any action by the assginee.  If there is a better way to do this, then please share!  Thanks

  37. Anonymous

    Request:

    I want to search on labels, if it contains a particular label.

    Right now, only "=" works.

    1. Did you try the IN operator? This should work:

  38. When using JQL with auto-complete switched on, searching for fields will always list global values. For example, a user that only has access to one particular project (say, with no Custom Fields used) will be presented with an auto-completed offer of all existing Custom Fields. The same holds for issue types, statuses, etc. For instance, when using the IN operator in JQL, auto-complete will "give away" values for fields that should not be accessible for our user. Given that there are schemes restricting the available fields for individual projects, this behaviour seems to be unintended with regard to usability or security concerns.

    As a user, I want the auto-complete function to only present field values that exist for "my" projects.

    • (With "my" meaning: projects, I have permission to browse or field values used in a scheme configuration for that project).

    Is this something anyone else has taken issue with? It seems that the JQL behaviour with regard to field values is not well or documented at all. At least I could not find any resources or discussions about this.

    Update: I opened an issue for this:

    JRA-36881 - Improve filter behaviour: auto-complete should not give away field values Open

    1. Yes I see the same issue.

  39. Can you please remove the documentation related to searching on attachments because it cannot be done.  It can only be done via a paid plugin and Atlassian shouldn't claim that they support the feature.

    1. I personally don't understand your request. The search IS EMTY || IS NOT EMPTY works as documented. Yes, it's a real pity, that the standard software itself doesn't support more search queries / operators for that type

      feel free to vote e.g. for

      JRA-5700 - Search for issues with attachment (by attachment presence) Open

      or

      JRA-1210 - Allow searching of attachments Open

      1. You cannot search for issues that have or do not have attachments.   Sure, IS EMPTY and IS NOT EMPTY are valid criteria.  But, if you try to use that with the attachments as indicated above, you get an error that attachments field is not valid.  Consequently, it should not be in the documentation.  We have tried it without success and input a support issue.  And according to this post:   https://answers.atlassian.com/questions/58558/search-and-show-all-tickets-that-have-attachments
        and this comment:  https://confluence.atlassian.com/display/JIRA/Advanced+Searching?focusedCommentId=317196433#comment-317196433
        JIRA will not let you search for attachments out of the box, as indicated in this documentation.  The only way we can search if an issue has or does not have attachments is with the JQL Tricks plugin.  We shouldn't have to purchase a plugin for something that Atlassian is indicating that they support.  They should either remove the documentation or list it as a known issue and fix it.  We are on the most current version of JIRA.

        1. Hi Karie,

          Which version of JIRA are you using? The 'attachments' JQL function was introduced in JIRA 6.2. I just tested it myself and it works. If you are using JIRA 6.2 and cannot get this function to work, please raise a support request.

          Kind regards,
          Andrew 

  40. Anonymous

    hello good morning am from Mexico I would like to help me with a problem with sub-filters to show labels on the kanban could help?

    Sub-filters

    fixVersion in unreleasedVersions() OR fixVersion is EMPTY

    *fixVersion does not exist and does not have permission to view.

  41. How  can I  count Jhon treated the question type and number and display like this

     isssuetype1isssuetype2countnumber
    Jhonnumber1number2number3


     

  42. Hello, for a specific SLA (first-respond-timer), I need to see if the status changed (from Open) maximum 2 hours after the creation of the ticket.

     

    I tried several things via the CHANGE element, like :

    status changed from Open DURING (created,created +2h), but unfortunately 'created' is not accepted there...

     

    So my question is : how to track the fact that the first-reponse (for example via a status change, or via a first-comment) has indeed been done in the 2-hours delay ?

     

    Thank you for your tips (smile)

    Alain

    1. (info) Yes, something like this is not possible, because JIRA doesn't allow comparisions between fields atm. (see discussions above or in JRA-20727 - Add ability to compare date fields using JQL Open )

      Also didn't tested it, but sounds like it covers your convern: https://marketplace.atlassian.com/plugins/com.innovalog.jmcf.jira-misc-custom-fields which has calculated date / time fields.


      You might just set up a (hidden) field for that, that is filled by workflow transition from Open to X. Then you might query for it. 

      (warning) but be aware, this one is a custom field from the JIRA charts that has a date value and therefor will not work for you because it's a (absolute) date field.

       

      Another idea often used / seen as a workaround: 

      create a query that covers all newly created issues, not updated for over 2h

      or using the changed query

      or the JIRA Charting Plugin has some custom fields that might help:

      then: set up notifications for that. But yes, this will not give you the power of JIRA and reports are only temporary available ;/