Closed
Bug 296145
Opened 20 years ago
Closed 19 years ago
saved search from "Find a Specific Bug" does not remember product
Categories
(bugzilla.mozilla.org :: General, defect, P3)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
FIXED
People
(Reporter: ispiked, Assigned: justdave)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050523 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050523 Firefox/1.0+ Do a search from "Find a Specific Bug" then try to save that search. The saved search does not remember the Product you chose from the "Product" drop-down menu. Reproducible: Always Steps to Reproduce: 1. Go to https://bugzilla.mozilla.org/query.cgi?format=specific 2. Select a Status from the status menu. 3. Select a Product from the drop-down menu. 4. Perform the search. 5. Save the search at the bottom with any name. 6. Under Prefs > Saved searches choose to edit the search. You will see that the product you chose is not remembered. Actual Results: Product selected is not remembered. Expected Results: The product you selected is remembered.
Comment 1•20 years ago
|
||
Specific to bmo. I cannot reproduce using the latest CVS version. Maybe is it related to their customised menu?
Assignee: user-accounts → justdave
Status: UNCONFIRMED → NEW
Component: User Accounts → Bugzilla: Other b.m.o Issues
Ever confirmed: true
Product: Bugzilla → mozilla.org
QA Contact: default-qa → myk
Version: unspecified → other
| Assignee | ||
Comment 2•20 years ago
|
||
I'm pretty sure this is an upstream bug in Bugzilla that has been fixed since we last upgraded, but I can't seem to find the original bug. I'll leave this here regardless as a reminder, since the change would need to be merged with our custom template anyway.
Blocks: bmo-upgrade-051022
Priority: -- → P3
| Reporter | ||
Comment 3•20 years ago
|
||
So what are the steps we could take to get this fixed? Is it as simple as applying a patch to the existing Bugzilla version we're running? Or would we completely have to reinstall and update it?
| Assignee | ||
Comment 4•20 years ago
|
||
(In reply to comment #3) > So what are the steps we could take to get this fixed? Is it as simple as > applying a patch to the existing Bugzilla version we're running? Or would we > completely have to reinstall and update it? Applying a patch would work. If we can't find the original bug, we'll have to figure out a new patch manually though. Shouldn't be too hard, but I'm travelling for the weekend. I'll look at it this next week.
| Assignee | ||
Comment 5•19 years ago
|
||
Fixed with tonight's upgrade. This was due to our local hack.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
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
•