Note: Projects (beta) is currently in public beta and subject to change.
About filtering projects
You can customize views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. For more information, see "Customizing your project views."
To filter a project, click and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the command pallet and type "Filter by" to choose from the available filters.
The same filters are available for insights, allowing you to filter the data used to create your charts. For more information, see "Using insights with projects."
Syntax for filtering projects
- To filter for any match of multiple values (an OR query), separate the values with a comma. For example
label:"good first issue",bug
will list all issues labelledgood first issue
orbug
. - To filter for the absence of a specific value, place
-
before your filter. For example,-label:"bug"
will only show items that do not have the labelbug
. - To filter for the absence of all values, enter
no:
followed by the field name. For example,no:assignee
will only show items that do not have an assignee. - To filter by state, enter
is:
. For example,is: issue
oris:open
. - Separate multiple filters with a space. For example,
status:"In progress" -label:"bug" no:assignee
will show only items that have a status ofIn progress
, do not have the labelbug
, and do not have an assignee. - To filter for the previous, current, or next iteration of an iteration field, use
@previous
,@current
, or@next
. For example,sprint:@current
. - To filter for items assigned to the viewer, use
@me
. For example,assignee:@me
. Anyone using this view will see items assigned to themselves. - To filter date and number fields, use
>
,>=
,<
,<=
, and..
range queries. For example:target:2022-03-01..2022-03-15
. For more information, see "Understanding the search syntax."