The latter. See request 5921, though.

Is this resolved in the sense of "quick searches are now available and 
can be named" or in the sense of "canceled because quick searches have 
been removed"?

What was done was removing saved quick searches. I'm open to saved 
quick searches, but I'd rather have a quicker and easier to use query 
builder.

Chuck, which is done: naming quick searches or dropping the quick  search feature?

From in the field observation, our clients use quick searches all the 
time.  The Query Builder scares them (power = learning curve = no time 
for training).

From an implementation standpoint, I think named quick searches 
should be kept and shown, but anonymous quick searches should be 
dropped.  If I'm not going to name it, I'm not going to need it again. 
  If I bother to name it, I will use it again.

Quick comparison (approximate times here, back of the napkin kind of thing):
* 4 seconds to decode a string like "Queue: Application: AERES, 
Category: Unconfirmed, New, Assigned, Type: Any, Summary: IE"
* 3 seconds to strike Alt+S, click twice and type IE.
* 2 seconds to strike Alt+End (Quick searches is at the bottom in my 
configuration) then 1 click to quick search named "IE bugs in AERES"

Done.

Agreed. I only used them once in a while, and they tend to grow to a 
very large list, while it's almost unusable once there are more then 3 
or 4 searches.

I was wondering if this feature should be dropped, honestly. You can 
already create and name queries, and they are much more powerful.

And I pretty much never use the saved searches, which is a big 
indicator to me that they're not doing much.

Other opinions?

It's very difficult to tell, at a glance, what a quick search will 
return.  The ability to name a quick search would make it far easier 
to scan the list of available quick searches and run the appropriate 
one.