I would like to be able to filter the list of items awaiting approval to those I am able to test. I would like to pick from dropdowns to pick Firefox 1.0, Windows, Themes

This lies outside of ideal, but isn't in itself bad. Filtering items does tend to promote missed entries in the queue which need to be looked at. Hiding those makes it easy (too easy, IMO) to ignore items. By default, it should always be a full-list, it's designed to be effective, not to special-case for each editor who wishes only to do /some/ of them and ignore others. Either way, not for update-beta, and I'm not interested in it. --> nobody.

I might implement it, but don't assign it to me - I don't have any time.

It is just like I cherry-pick my bugzilla list of things to test. If I have the time/energy, I don't care. If I don't have the right application, I definitely care. I have seen as many as 60 items waiting to be tested in bugzilla. This would also give us a good way to see if we need to employ more testers for a certain area.

Bulk Moving Developer Control Panel bugs to new component. (Filter: massdevcpspam)

I'd also vote for doing this. After all, Macintosh users can't test Win32-only XPIs, and Firefox users who don't have Thunderbird won't be able to test Thunderbird extensions... Besides this, people may like to help out in a certain area - I, for example, am helping out with Thunderbird extensions, 'cause there should be enough Firefox testers anyway, but too few for Tb. So filtering for "Thunderbird" or even "Win32 Thunderbird" would be ideal for me (currently, I do this with a customized Bugzilla query).

AMO bugspam. Correcting QA contacts on OLD bugs (mozilla.update@update.bugs) -> Correct QA contact (developers@add-ons.bugs) Filtermeplzkthx

Fligtar's on this in Remora.

I think this is fixed in remora

"Filters are not yet functional!"

I'm forward duping because the new bug has more specifics