I was just about to make an issue for this. I think something very simple but extensible for the future could be to just copy github's filter text bar. Something like this with a default set to filter to your own workspaces.

Yeah, I think that filter syntax has all the power we need for the foreseeable future and will be familiar to our users. I'm not sure how difficult it is to implement though. I suppose we could implement it term-by-term and it would be pretty straightforward.

It would also be nice if when you clicked "f0ssel" it filtered for "f0seel", same with status, template, etc.

Even simpler would be just a prefix string search. I don't think we even need a syntax. Having that implies having to support it in the future.

Even simpler would be just a prefix string search. I don't think we even need a syntax. Having that implies having to support it in the future.

I think we'd want a default filter set to "me" so it shows your own workspaces by default, and that simple approach would not handle that unless the field was specifically for filtering by user and not by workspace name or anything else.

I'm used to that kind of thing being a checkbox e.g.
[ ] Show everyone's workspaces

I lean towards the search syntax since one term is easy to implement and the approach is in line with our medium term needs.

We want our large multi thousand user customers to switch this year so we have to be careful about excessive incrementalism with these table features.

The need for the checkbox won't go away with a more powerful search syntax. There are lots of search features that have UI elements that duplicate search syntax elements, e.g. GitHub search, Google, Indeed, Twitter, and more. You need the search syntax for the power users and the UI elements for everyone else.

I made a frontend only poc of the query filter I think someone could clean up nicely - #1936