Same!

@ankneis Sorry for the direct ping, but you seem to consider this feature to be released according to your comment here: github/roadmap#928

Now that I understand you were working on a very specific "Issues" project I understand that this might not have been part of the project scope and roadmap issue, but are there any plans to release this filtering for "Projects" as well? I never really need AND or OR in normal issue filtering, but I need it daily in my project views... Having inconsistent behaviour across these issue filter bars is quite confusing.

Just noting that this feature, as is, is essentially useless for our org's workflows. It would however be very valuable in projects/project search.

+1 was excited to try this feature, but unfortunate to find out it's not yet supported for project queries. Is this on the future roadmap?

We are using these tools extensively on the Auro Design System team at Alaska Airlines. However, we rely primarly on the project views as each of our web components is in it's own repository. I was very jazzed about the advanced search features and equally deflated when I saw that they don't work in projects. I see this conversation goes back 3 months. Would love to know if project support is even being considered.

Also linked/cross-posted in https://github.com/orgs/community/discussions/139935#discussioncomment-10851387

Thank you for sharing this feedback, as noted on the other discussion we're looking into it 👍

Noted this feedback, thank you!

A bit more feedback here on why bookmarking advanced searches is critical. One key use case is triaging issues that don’t yet have a project assigned. Advanced search enables us to add criteria not available in project views, like filtering for all issues without a project. This is essential for handling incoming bugs or alerts created by tools like Datadog or Freshdesk. These issues are added directly to the repository but don’t automatically get assigned to a project.

Without a way to bookmark this search view, we lose efficiency in managing these unassigned issues. Bookmarking would allow us to treat this view as a triage dashboard, making it easy to regularly revisit, organize, and assign these issues to the right projects. It’s a simple feature that could have a massive impact on improving workflows for teams managing high volumes of incoming requests.

Thank you for this feedback, we have it noted! Correct that once you type n you will see the No dropdown appear.

Thank you for reporting this! We'll look into this and will provide an update when we have more details 👍

Searching for multi-word strings no longer works properly.

Heck-- searching for single-word strings no longer works properly.
It returns completely unrelated results where the word in question occurs nowhere in the issue.
Search is basically broken.

[edit]
Actually-- it appears it isn't broken. It's just searching deep into collapsed <details> elements as are commonly used for listing technical details in bug reports, like what software users have installed on their environment; technical logs; etc.
Maybe not search and index in those?
Or at least not return results based on those by default ?

Looks like quoted phrases are finally working!

We just pushed a fix this week! Let us know if you encounter this in the future 👍

is:pr is a nice tip, thanks!

Thank you for sharing this feedback! Noting that you can filter by the number of reactions, just not the specific reaction type 😄

When I want to get a list of issues that I'm interested in, my own reaction is far more helpful than the number of reactions from other people.
This is especially useful for open source projects with a slow release cycle where I don't want to join the discussion (so subscribing is not an option) but check regularly whether certain bugs have been fixed.

Any update on this?

Not quite yet, but I'll be sure to post here when this is resolved!

We just pushed a fix on this, @L-Clouds could you try again and let us know if you are still seeing this issue?

Oh, I didn't see the reply just above when I came to write this:

Discovered that there's been progress on this! It looks like NOT works again, now, although it doesn't work for quoted phrases, instead using only the first word therein - but that looks like a separate issue covered under this comment: https://github.com/orgs/community/discussions/139934#discussioncomment-10930535

Yes we're working on a fix for that one currently, expect to see this fixed soon 😁 I'll post an update when it's resolved!

[edit] never mind.
It appears that the search term is actually present in the collapsed extensions in the opening post.
Looks like this is a thing where Firefox does not offer search through collapsed text.

With that, maybe another suggestion is in order:
Don't search in collapsed <details> elements by default - because most of the time you're going to get this kind of thing where tangentially related stuff is going to be present in a log file and it's just going to lead to a lot of false positive hits.

We now support has:type as a filter from the repository page. We're working on updating the documentation to reflect this. Let us know if you see any issues.

I'll provide an update when we support advanced issue searching via the API 👍 Thank you for your patience on this!