Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

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:

Search Term

Description

Examples

my

Find issues assigned to me.

my open bugs

r:

Find issues reported by you, another user or with no reporter, using the prefix r: followed by a specific reporter term such as me, a username or none.

Note that there can be no spaces between "r:" and the specific reporter term.

r:me — finds issues reported by you.
r:samuel — finds issues reported by the user whose username is "samuel".
r:none — finds issues with no reporter.

<project name>
or
<project key>

Find issues in a particular project,

test project
TST
tst

overdue

Find issues that were due before today.

overdue

created:
updated:
due:

Find issues with a particular Created, Updated, or Due Date using the prefixes created:, updated:, or due:, respectively. 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 have spaces in them. Valid date/time abbreviations are: 'w' (week), 'd' (day), 'h' (hour), 'm' (minute).

created:today
created:yesterday
updated:-1w — finds issues updated in the last week.
due:1w — finds issues due in the next week.
due:-1d,1w — finds issues due from yesterday to next week.
created:-1w,-30m — finds issues created from one week ago, to 30 minutes ago.
created:-1d updated:-4h — finds issues created in the last day, updated in the last 4 hours.

<priority>

Find issues with a particular Priority.

blocker
major
trivial

<issue type>

Find issues with a particular Issue Type. Note that you can also use plurals.

bug
task
bugs
tasks

<resolution>Find issues with a particular Resolution.

fixed
duplicate
cannot reproduce

c:

Find issues with a particular Component(s). You can search across multiple components.

Note that there can be no spaces between "c:" and the component name.

c:security — finds issues with a component whose name contains the word "security".

v:

Find issues with a particular Affects Version(s). To find all issues belonging to a 'major' version, use the wildcard symbol '*'.

Note that there can be no spaces between "v:" and the version name.

v:3.0 — finds issues that match the following versions (for example):

  • 3.0
  • 3.0 eap
  • 3.0 beta

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

ff:

Find issues with a particular Fix For Version(s). Same usage as v: (above).

 

*

Wildcard symbol '*'. Can be used with v: and ff:.

v:3.2* — finds any issue whose version number is (for example):

  • 3.2
  • 3.2-beta
  • 3.2.1
  • 3.2.x
Icon

In Mozilla-based browsers, try creating a bookmark with URL http://<your-JIRA-site>/secure/QuickSearch.jspa?searchString=%s (substituting <your-JIRA-site> with your JIRA site's URL) and keyword (such as 'j'). Now, typing 'j my open bugs' in the browser URL bar will search your JIRA site for your open bugs. Or simply type your search term in the Quick Search box, then right-click on the Quick Search box (with your search term shown) and select "Add a Keyword for this search...".

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
Icon

Note that you can combine free-text and keywords together. For example, 'my closed tst tasks', 'open test bugs pear', 'closed test bugs ' are all valid search queries.

Searching JIRA issues from your browser's search box

If you are using Firefox or Internet Explorer 8, you can add your JIRA site as a search engine/provider via the dropdown menu next to the browser's search box. 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.

 

OpenSearch

Icon

JIRA supports this browser search feature as part of the autodiscovery part of the OpenSearch standard, by supplying an OpenSearch description document. This is an XML file that describes the web interface provided by JIRA's search function. Any client applications that support OpenSearch will be able to add JIRA to their list of search engines.

20 Comments

  1. Anonymous

    how to search N number of issues reported by different reported in a single search?

  2. Is it possible to search by label?

  3. Hi there,

    is there any way (even plugin development), how to translate smart query keywords like "my, due" etc.?

     

    Thanks for reply

  4. any way (or already a feature request) regarding: How can I negate my search.

    will fail

    also excluding states is not possible:

    should do something like

  5. Anonymous

    Using c: with multiple components is unclear:

    Where c:A finds the component,

    c:A c:B

    does not work, neither does

    c:A,B

    (given components which are named 'A the first component' and 'B the second component')

    How to search for A or B?

    1. Just: No, the quick search is often very primitive and as you can see above, logical conditions are not possible. Perhaps there is an issue for that (see http://jira.atlassian.com) or already another plugin discussed on http://answers.atlassian.com

  6. We have JIRA v4.4.4#664-r167664 and I'm using Firefox 14.0.1 – I don't get the "Add JIRA site" as a search engine provider in the search box dropdown menu. Does this feature no longer work?

    I had gotten very used to this feature on Chrome (seems as Chrome just automatically added the JIRA search engine, I discovered it by accident!), but I'm trying to switch to FF because Chrome doesn't work with Confluence's "Edit in Word" feature (no WebDAV).

    1. Anonymous

      I ran into the same problem today when setting up a new software installation using JIRA v4.4.1#660-r161644 and Firefox 14.0.1. Confluence shows up automatically as a possible search engine, but JIRA does not.

       

      As quick fix you can add it to Firefox manually. For that you need to add an xml (probably named after your JIRA site) file of JIRA search provider to either (applies to your user) your own Firefox profile folder "...your_profile\searchplugins\" or (applies to all users) to global installation folder "...firefox\searchplugins\". You should be able to use exatcly the same xml file from somewhere inside your chrome installation. I had one from my prevous Firefox installation. In case you don't find it, there are guides on how to create a new xml manually (for example: http://www.singhvishwajeet.com/2009/03/09/how-to-add-jira-quick-search-to-firefox-search-provider/).

       

  7. A colleague and I had mixed results. It worked for me just fine and didn't for him. We then found that the difference was that he was trying to add the search engine while viewing the JIRA dashboard page while I was browsing an issue at the time. I asked him to try again from an issue page and it then worked.

    edit: JIRA 4.4.4 and Firefox 14.0.1

  8. Anonymous

    I can't search for a specific assignee in QuickSearch, can I?

     

    1. unfortunately not:

      JRA-26255 - Add Assignee to Quick Search Resolved

      Great suggestion - unfortunately we don't have plans to make improvements to quick search. Our current efforts and focus are on improving the Simple and Advanced Search UI.

      Cheers,

      JIRA Product Management

      (thumbs down)

  9. Anonymous

    We used to be able to search for numbers that appear in a ticket's description using quick search. But recently this stopped working. This is a known bug?

    1. Hi,

      I'm not aware of any known bugs with the Quick Search. Can I ask you raise a support request at https://support.atlassian.com? If you don't have an account on https://support.atlassian.com, you can sign up for one for free.

      Kind Regards,
      Andrew

  10. Is it possible to search for tickets that had an updated due date within a specific period of time?

  11. Is it possible to kill the smart search feature?

  12. I think this page needs an update. As I learned from  JRA-7686 - Allow text custom fields to be searched from quick search / text search. Resolved  it's possible to search in every custom text field using quick search since JIRA 5.2.

  13. Anonymous

    How can I create a filter (in agil boards) which shows me my open issues (which are assigned to me) plus all issues in a project which are observed by me??

     

    Thanks for your help.

    With best regards

     

  14. Anonymous

    We recently did a massive import of very old Bugzilla issues.  Users who are used to working only in Bugzilla are frustrated that they can't simply type in the old Bugzilla issue number into quick search to find issues.  We've stored these numbers at the External Issue ID.  Is there a way we can tie searching in the quick search box to that field?  At the moment, it will work if the issue happens to be in the active project, but it fails angrily otherwise.  Would it be possible to have something like "e:<external issue ID>" effectively do the same thing as "External issue ID" ~ "<external issue ID" in advanced search?

  15. Is it possible to quickly search for all issue types except bugs? 

    "searchterm task" works, but only shows tasks and no new features or improvements
    "searchterm bugs" works, but does the opposite of what i want
    "searchterm new feature" does not work

    Something like "searchterm !bugs" would be great, but does not work - is there a way to do this? I know i alway can use advanced search...