Using Quick Search

Sometimes you just want to be able to get to the particular issue that you are interested in. Other times you can't remember what the issue was, but you remember that it was an open issue, assigned to you. Quick Search can help you.

On this page:

Jump to an Issue

The Quick Search box is located at the top right of your screen. If you type in the key of an issue, you will jump straight to that issue. For example, if you type in 'ABC-107' (or 'abc-107'), and press the Enter you will be redirected to the JIRA issue 'ABC-107'.

In many cases, you do not even need to type in the full key, but just the numerical part. If you are currently working on the 'ABC' project, and you type in '123', you will be redirected to 'ABC-123'.

Smart Querying

Quick Search also enables you to perform 'smart' searches with minimal typing. For example, to find all the open bugs in the 'TEST' project, you could simply type 'test open bugs', and Quick Search would locate them all for you.

Your search results will be displayed in the Issue Navigator, where you can view them in a variety of useful formats (Excel, XML, etc).

The search terms that Quick Search recognises are:

• Issues assigned to me — You can use the keyword 'my', as in 'my open bugs'.
• Issues with a particular reporter (available in JIRA version 4.3+) — You can search for issues reported by you, with no reporter, or reported by a specific user. Examples:
  • 'r:me'
  • 'r:none'
  • 'r:samuel' — if 'samuel' is the username you are searching on.
• Issues in a particular project — To find all issues in a project, type the project name, e.g. 'test', or the project key, e.g. 'TST' (or 'tst').
• Overdue issues — You can use the keyword 'overdue' to search for issues that were due before today.
• Issues with a particular Created, Updated, or Due Date — You can find issues with certain dates. You can use the prefix created:, updated:, or due:. For the date range, you can use today, tomorrow, yesterday, a single date range (e.g. '-1w'), or two date ranges (e.g. '-1w,1w'). Note that date ranges cannot spaces in them. Valid date/time abbreviations are: 'w' (week), 'd' (day), 'h' (hour), 'm' (minute).
  Some examples:
  • 'created:today'
  • 'created:yesterday'
  • 'updated:-1w' — issues updated in the last week
  • 'due:1w' — issues due in the next week.
  • 'due:-1d,1w' — all issues due from yesterday to next week.
  • 'created:-1w,-30m' — all issues created from one week ago, to 30 minutes ago.
  • 'created:-1d updated:-4h' — all issues created in the last day, updated in the last 4 hours.
• Issues with a particular Status — You can use the name of any status in your search, e.g. 'open', 'closed'.
• Issues with a particular Resolution — You can use a resolution name to search for issues with a particular resolution, e.g. type 'duplicate' to search for all issues that have a resolution of "Duplicate". You can also use the keyword 'unresolved' to find all issues that do not yet have a resolution.
• Issues with a particular Priority — You can type a priority name to search for issues with a particular priority, e.g. 'blocker'.
• Issues of a particular Issue Type — You can use the type of an issue in the search. Examples include bug, task. Note that you can also include plurals, such as bugs.
• Issues with a particular Version — You can use the prefix "v:" to search for issues with a particular version(s). Note that there can be no spaces between "v:" and the version name. "v:3.0" will match against the following versions (for example):
  • 3.0
  • 3.0 enterprise
  • 3.0 standard
    but will not match against the following versions (for example):
  • 3.0.1
  • 3.0.0.4
    That is, it will match against any version that contains the string you specify followed immediately by a space, but not against versions that do not contain a space immediately after the string you specify.
• Issues with a particular Fix For Version — You can use the prefix "ff:" to search for issues with a particular fix for version(s). The search mechanism is the same as the quick search for Issues with a particular Version.
• Issues with a particular Component — You can use the prefix "c:" to search for issues with a particular component(s). This allows you to search across multiple components. "c:security" will search for all issues with a component that contains the word "security". Note that there can be no spaces between "c:" and the component name.

Free-text searching

You can search for any word within the issue(s) you are looking for, provided the word is in one of the following fields:

• Summary
• Description
• Comments

Note that, unlike the keywords listed under 'Smart Querying' above, free-text search works in both the Quick Search box and the Issue Filter Text Search box.

Searching JIRA issues from your Browser's Search Box

If you are using Firefox or Internet Explorer 7 or later, you can add your JIRA site as a search engine/provider via the dropdown menu next to the browser's search box.

The example below shows a JIRA site called "Example Company JIRA Site", which is offered for inclusion as a search engine/provider in the browser's search box, when you visit that site.

Once you add your JIRA site as a search engine/provider in your browser, you can use it at any time to conduct a Quick Search for issues in that JIRA site.