I would love some pro-shorthand  for search. For example:

"OT: quack"

Seaches open tasks with quack

"CD: quack"

Searches closed diffs with quack

"T: quack"

Searches any task with quack

Anywho, I never get what I want from the first search, and usually have to flip switches. Maybe something like this already works though, I am bad at knowing the product sometimes.

I ran into a bunch of mess actually getting the implementation working the way I wanted, and I'm not sure it would be good even if we did get it working. Part of the reason that it's difficult is that we render the menu before executing the query right now, so we don't have an opportunity to add on any ?query=whatever stuff. Some of this difficulty is just the infrastructure working in a sort of silly way right now, but some of it seems hard to implement cleanly without special casing this sort of thing.

Maybe I'll just do the "when you type stuff into the menu bar, we overwrite the query of your first/default filter, and execute that" (which seems mostly reasonable and is easy), but not do "when you navigate from that page to other filters, we'll carry the query along" (which might be useful, but starts to get kind of weird/unexpected, and ends up being really messy to implement).

It would be fairly easy to do "ot:", but I worry it will go virtually unused because it won't be discoverable (for example, you can already type "task: xyz" to prefill a task, but I'd guess zero people know about or use it). The driving use case here (from @bigo) is a desire to make global search mean "open tasks" by default.

Id use it at least, would you though? I would pay for that feature. Several tokens. :D

(I'm holding this until I can set up ElasticSearch and verify I didn't break anything on that pathway.)