GitHub Projects Advanced Search: AND, OR and Review Filter Examples

GitHub Projects now supports advanced search with explicit AND and OR operators in a project view’s filter bar. GitHub also added a reviews: filter for pull request review state. Open a project view, click the filter bar, and type an expression; use the copy-paste patterns below as starting points, then replace sample field values with values from your own project.

Quick setup checklist

1. Open the GitHub Project and select the table, board, or roadmap view you want to filter.
2. Click the filter bar. You can also open the command palette with Command+K on macOS or Ctrl+K on Windows/Linux and choose Filter by.
3. Start with one verified field filter, such as assignee:@me, is:pr, status:"In progress", or no:assignee.
4. Combine clauses with the new uppercase AND or OR operators.
5. Check the returned items before saving or sharing the view.
6. Save the filtered layout as a project view when it represents a recurring workflow.

Copy-paste GitHub Projects filter examples

Field names and values can differ between projects. Keep quotation marks around values containing spaces, and replace example repositories, labels, statuses, and custom fields with your own.

Goal	Filter to start with
My open work	assignee:@me AND is:open
Open bugs or open support items	(is:open AND label:bug) OR (is:open AND label:support)
Unassigned, unlabeled triage queue	no:assignee AND no:label
Pull requests assigned to me	is:pr AND is:open AND assignee:@me
Work in either of two repositories	repo:octocat/app OR repo:octocat/api
Current and next three iterations	iteration:@current..@current+3
Items due in the next seven days	date:@today..@today+7
Open work without a priority	is:open AND no:priority
Bug or onboarding label	label:bug,onboarding
Exclude completed work	-status:done

Important: GitHub’s July 16 announcement confirms that explicit AND and OR expressions are now generally available in Projects. GitHub’s filtering documentation may still show older wording that says cross-field logical OR is not supported. If a sample behaves differently in your project, use the filter bar’s suggestions and test the smallest clause first; the product announcement is newer than that documentation wording.

How the new AND and OR operators help

Previously, teams often created separate project views for closely related questions. For example, one view might show open bugs and another open support requests. Explicit logical operators let you express more of that logic inside one filter.

• AND narrows results to items that satisfy both sides.
• OR broadens results to items satisfying either side.
• Parentheses make mixed logic easier to read and reduce ambiguity.
• Uppercase operators visually separate logic from field names and values.

Start with simple filters before building a long expression. If label:bug and is:open each work independently, combine them only after confirming both return the expected items.

Using the new reviews filter safely

GitHub’s announcement says project views can now filter pull request items by review state with the new reviews: search filter. It is backed by the Reviewers field, which tracks who was requested to review and the latest review submitted by each person.

Because accepted review-state values can be exposed by the project filter bar and GitHub’s current public filtering page does not yet list them in the extracted documentation, the safest workflow is:

1. Open a project view containing pull requests.
2. Type reviews: in the filter bar.
3. Select a state offered by GitHub’s autocomplete instead of guessing a token.
4. Add is:pr and other clauses after confirming the review-state filter works.
5. Check a few matching pull requests manually, especially when review requests have changed.

Do not confuse reviews: with reviewers:. GitHub documents reviewers:USERNAME for filtering by a reviewer, while the newly announced reviews: filter targets review state.

Useful existing GitHub Projects qualifiers

Qualifier	What it does	Example
assignee:	Filters by assignee	assignee:@me
reviewers:	Filters by reviewer	reviewers:octocat
label:	Filters by label	label:bug
repo:	Filters by repository	repo:octocat/game
is:	Filters by state or item type	is:open or is:pr
has:	Requires a field value	has:assignee
no:	Finds a missing field value	no:priority
-	Negates a filter	-status:done
updated:	Filters by modification date	updated:@today

Build a practical triage view

A useful first view is an open-item triage queue. Build it in small steps:

1. Enter is:open.
2. Add AND no:assignee.
3. Add AND no:label if labels are required in your workflow.
4. Add a repository clause when one project spans multiple repositories.
5. Review the result, name the view clearly, and save it.

A basic version is:

is:open AND no:assignee AND no:label

For a project spanning two repositories, test a grouped expression such as:

is:open AND no:assignee AND (repo:octocat/app OR repo:octocat/api)

Replace the sample owner and repository names. If the full expression does not behave as expected, test each repository clause and the grouped OR separately before recombining them.

Deployment status retention also changed

The same GitHub changelog entry announces a new 90-day retention policy for deployment statuses. Statuses older than 90 days are automatically deleted and no longer appear through the REST or GraphQL API. GitHub says a deployment’s current state is not affected.

If you export deployment history for audit, reporting, or internal dashboards, review that workflow now. Do not assume every historical status will remain queryable indefinitely through GitHub’s APIs.

Troubleshooting checklist

• No results: remove clauses one at a time and verify the exact field values used by the project.
• A value contains spaces: quote it, for example status:"In progress".
• A custom field fails: start typing its name and choose the suggestion shown by the project filter bar.
• OR behaves unexpectedly: add parentheses and test each side separately.
• Review filtering is unclear: type reviews: and choose an autocomplete value rather than inventing one.
• Documentation appears inconsistent: compare the July 16, 2026 changelog with the current filtering documentation; rollout-related documentation can lag a new generally available feature.

FAQ

Does GitHub Projects support AND and OR filters?

Yes. GitHub announced on July 16, 2026 that advanced search with logical AND and OR in the filter bar is generally available for GitHub Projects views.

Where do I enter an advanced Projects filter?

Enter it in the filter bar of a GitHub Project view. You can also open the project command palette with Command+K on macOS or Ctrl+K on Windows/Linux and choose Filter by.

What is the difference between reviews and reviewers filters?

GitHub describes the new reviews: filter as filtering pull requests by review state. The documented reviewers:USERNAME qualifier filters by reviewer identity.

Can I save an advanced filter as a view?

GitHub Projects lets you combine filters and save filtered layouts as views. Validate the results before treating the view as an operational queue.

What happens to deployment statuses older than 90 days?

GitHub says statuses older than 90 days are automatically deleted and stop appearing in the REST and GraphQL APIs, while the deployment’s current state remains unaffected.

Sources

• GitHub Changelog: Advanced search for Projects is generally available
• GitHub Docs: Filtering projects
• GitHub Community announcement and feedback discussion

Editorial note: This guide is based on GitHub’s official announcement and documentation checked on July 17, 2026. Project fields and allowed values can vary by project, and GitHub documentation may be updated after rollout.