Here's my problem in story form: I finally decided that it was time to remove all my 2.18 saved searches. I remembered reading about or seeing a place to do that other than the query screen, so I figured I'd check out User Prefs to see if that was it. It was in there (should we make that more obvious somehow?), so I clicked the Forget link and it brought me to a page that said the query was gone. But there was no link to the Saved Searches page, only to the query page. So I had to do the footer than tab link thing again.

As soon as bug 282130 is fixed, we won't need to go to buglist.cgi anymore. We will be able to remain in userprefs.cgi while deleting the saved search.

This bug is retargetted to Bugzilla 3.2 for one of the following reasons: - it has no assignee (except the default one) - we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1) - it's not a blocker If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0. If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug. If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2. This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.