- If you don't have complex search criteria, try quick search instead.
- If you're comfortable with the Jira Query Language (JQL), you can try the advanced search.
Basic search
- Choose Search > View all issues.
If the advanced search is shown instead of basic, click Switch to basic. - Set your search criteria, like Project, Status, and Assignee.
- Optionally, enter text to search for and add more criteria by clicking +More.
- Click Search.
If you're searching against a field and can't find the field you want, or the field is displaying greyed out text, see the Troubleshooting section below.
When searching for text, you can use special characters and modifiers in your search text, such as wildcards and logical operators. See Search syntax for text fields.
What can stop me from switching between basic and advanced search?
In general, a query created using basic search will be able to be translated to advanced search, and back again. However, a query created using advanced search may not be able to be translated to basic 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.
- i.e. even though this query:
- 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 theAND 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 basic search form, then it will not be able to be translated from advanced search to basic search.
Run a saved search
Saved searches (also known as filters) are shown in the sidebar. To run a filter—for example, My open issues—click the filter name. If you can't see the sidebar, click the arrow below the Jira logo to expand it.
Clicking some filters, like the Viewed recently filter, will switch you to the advanced search as the basic search can't represent the ORDER BY clause in this filter.
Troubleshooting
Why can't I find the field I want to choose?
Some fields are only valid for a particular project/issue type context. For these fields, you must select the applicable project/issue type. Otherwise, the field is not available for selection.
Why are the field criteria displaying in gray text?
Some fields are only valid for a particular project/issue type context. If you choose a field in your search, then remove all projects/issue types that reference the field, then the field is invalid. The invalid field does not apply to your search and displays in grey text.
Why is there a red exclamation mark in my field?
Some field values are only valid for a particular project/issue type context. For example, you may have configured a project to use a status In QA Review in its workflow. If you select this project and status in your search, then change the search to filter for a project that doesn't use In QA Review, the status will be invalid and ignored in the search.
Why don't my search results automatically update?
Your search results will always update automatically whenever any fields are changed, provided that your administrator has not disabled automatic updates of search results. Ask your administrator whether they have disabled automatic updates of search results.
What happens when two of my fields are named the same?
Fields in next-gen projects are contained within the project itself. So, you can create fields with the same name in different projects. Learn more about custom fields in next-gen projects.
Refining your search criteria using the duplicate field names just got easier. Pick the right criteria for your search results based on the field type that shows up along with the duplicate field names.