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 project command palette, by pressing Command+K (Mac) or Ctrl+K (Windows/Linux), and type "Filter by" to choose from the available filters.
Using multiple filters will act as a logical AND filter. For example,
label:bug status:"In progress" will return items with the
bug label with the "In progress" status. Projects does not currently support logical OR filters across multiple fields.
The same filters are available for charts you create using insights for Projects, allowing you to filter the data used to create your charts. For more information, see "Using insights with projects."
When you filter a view and then add an item, the filtered metadata will be applied to added item. For example, if you're filtering by
status:"In progress" and you add an item, the new item will have its status set to "In progress."
Click at the top of the table to show the "Filter by keyword or by field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
- To filter for any match of multiple values (an OR query), separate the values with a comma. For example
label:"good first issue",bugwill list all issues labelled
good first issueor
- 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 label
- To filter for the absence of all values, enter
no:followed by the field name. For example,
no:assigneewill only show items that do not have an assignee.
- To filter by state, enter
is:. For example,
- Separate multiple filters with a space. For example,
status:"In progress" -label:"bug" no:assigneewill show only items that have a status of
In progress, do not have the label
bug, and do not have an assignee.
- To filter for the previous, current, or next iteration of an iteration field, use
@next. For example,
- 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 by when an item was last updated, use
last-updated:followed by the number of days. This filter only supports
1dayfor a single day) as a unit. For example,
last-updated:7dayswill only show items that were last updated 7 or more days ago.
- To filter date and number fields, use
..range queries. For example:
target:2022-03-01..2022-03-15. For more information, see "Understanding the search syntax."
- To filter for issues tracked by a specified issue, use
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"and replace
<OWNER>with the repository owner,
<REPO>with the repository name, and
<ISSUE NUMBER>with the issue number.
Alternatively, open the project command palette by pressing Command+K (Mac) or Ctrl+K (Windows/Linux) and start typing "Filter by."
In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.