Karl (comment #3) notes that the defaults might change; in this case I think they should and quite freely (and I do not see that as a problem). At the moment an "Advanced search" immediately defaults to a subset of the bug space, so the first thing is to tick the remaining Closed/Released/Expired... ideally these should be ticked by default—if a Simple search had found the answer, I would /not/ be resorting to the Advanced search screen.
Each keypress, or mouse click, I make should be about /narrowing/ the search space (rather than needing to expand it before narrowing).
The worry (about changing defaults) is I believe moot as at the moment—the URLs are generally too big to post/save/email for longevity anyway without modification; the URLs that /are/ making it into the wild with longevity (Pitti, comment #12) are those that /have/ been manually hand-hacked down to a usable length.
On top of mpt's estimated savings (comment #10), having "field.status:list=any" (insert of per-item enumeration) would remove most of the length, and then going further and having 'any' as default (per paragraph immediately above) but allow elimination.
Example copied over from duplicate. Since I only touched/modified one field, that is the only field that should be present, eg:
http:// bugs.launchpad. net/ubuntu- font-family/ +bugs?field. tag=uff- greek
Karl (comment #3) notes that the defaults might change; in this case I think they should and quite freely (and I do not see that as a problem). At the moment an "Advanced search" immediately defaults to a subset of the bug space, so the first thing is to tick the remaining Closed/ Released/ Expired. .. ideally these should be ticked by default—if a Simple search had found the answer, I would /not/ be resorting to the Advanced search screen.
Each keypress, or mouse click, I make should be about /narrowing/ the search space (rather than needing to expand it before narrowing).
The worry (about changing defaults) is I believe moot as at the moment—the URLs are generally too big to post/save/email for longevity anyway without modification; the URLs that /are/ making it into the wild with longevity (Pitti, comment #12) are those that /have/ been manually hand-hacked down to a usable length.
On top of mpt's estimated savings (comment #10), having "field. status: list=any" (insert of per-item enumeration) would remove most of the length, and then going further and having 'any' as default (per paragraph immediately above) but allow elimination.