Closed
Bug 274067
Opened 20 years ago
Closed 20 years ago
Saved searches created with older versions of Bugzilla cannot be forgotten.
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: morac, Assigned: justdave)
References
()
Details
Attachments
(1 file)
|
79.06 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Saved searches that were created using the older save search system in Bugzilla version 2.16.x cannot be forgotten once a site upgrades to Bugzilla version 2.17.x I have some old saved searches that do not have the new "&namedcmd=" parameter in the URL. They are the old type that stores the whole query in the URL. When these old versions of saved searchs are run there is no option to "forget search". The option is also not visible in the Edit Query page where it used to be in 2.16 I tried creating a new saved search with the same name as the old one, but that just created a brand new saved search with the same name. I also tried copying the link for forgetting one of my existing new searches and replacing the name with the old search's name, but that did not work. Reproducible: Always Steps to Reproduce: 1. Have an old saved search 2. Run it Actual Results: There is no option to forget the search. There is an option to edit it, but it can't be forgotten from that page either. Expected Results: There should be an option to remove older versions of saved searches or they should be automatically converted to the new version when they are run.
| Reporter | ||
Comment 1•20 years ago
|
||
Apparently the searches had to be created in an even older verison of Bugzilla (not version 2.16.x) since I'm experiencing the same problem trying to forget one of my old saves over at http://bugzilla.mozdev.org which runs 2.16.7. Basically any saved search that does not have a "namedcmd" save name cannot be forgotten. So any saved searches created before that feature was introduced will experience this problem. I'm attaching a screenshot of the problem. The "My Bugs" saved search was created under an old version of Bugzilla and cannot be forgetten. "All My Bugs" was created with the new version.
this is 'fixed' in some newer version of bugzilla which bmo isn't running.
| Assignee | ||
Comment 3•20 years ago
|
||
There's two problems listed here. First one: "My Bugs" is "special". It's not a saved query, it's a menu item that happens to show up in that slot. Once of these days we'll get rid of it, because it mostly seems to confuse people these days. In the mean time, there's supposed to be an option in your preferences to turn it off (in 2.16.x, it's the Page Footer panel in preferences, in 2.18 and up it's in the Saved Searches panel). That option is also missing in the version we're running currently, but it'll be there after we upgrade this weekend. Second one: No UI to delete a query that doesn't have any results. This is fixed in the version of Bugzilla we'll be upgrading to this weekend. In the mean time, you can manage your queries from https://bugzilla.mozilla.org/page.cgi?id=saved-searches.html Since this is fixed, but bmo doesn't have it yet, moving this bug to the mozilla.org product, and making it dependent on the upgrade.
Status: UNCONFIRMED → NEW
Component: Query/Bug List → Bugzilla: Other b.m.o Issues
Depends on: 244831
Ever confirmed: true
Product: Bugzilla → mozilla.org
QA Contact: mattyt-bugzilla → myk
Version: unspecified → other
| Reporter | ||
Comment 4•20 years ago
|
||
I didn't realize the "My Bugs" was not a saved search. In that case my bug report is invalid. Also since bmo is being upgraded tomorrow there's no point leaving the bug here so I'm withdrawing it
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•13 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•