Perform a quick search

Quick search lets you find issues, projects, boards, queues, and more, including items you’ve worked on recently. To perform a quick search:

  1. Select Search () in the navigation bar (or press / on your keyboard).

  2. Choose from recent items or type to search.

  3. Optionally, filter the search results by choosing a project or issue assignee.

  4. Select an item or continue to Advanced issue search (press enter on your keyboard).

Before you start typing, the quick search shows recent items you’ve worked with, like issues, projects, boards, queues, and filters.

The quick search dialog showing search results and filters.

The quick search field also lets you search more than just text. Here are some search commands you can use:

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

status

Find issues with a particular Status.

To Do
Backlog
Open

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

 

Additional Help

Ask the Community