Closed
Bug 266419
Opened 20 years ago
Closed 20 years ago
"my bugs" search failure
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: allltaken, Assigned: justdave)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910 I've reported 3 previous little non-duplicate bugs, and have made a number of comments. Recently I reported bug #265278 and then found that it does not show up on my saved searches of bugs or comments. Previous bugs and comments appeared in the lists as expected. The only way I'm able to get to recent reported bug is by the bug number or the link in the correspondence about it. Reproducible: Always Steps to Reproduce: 1. Report a bug (complete form, make sure the information is accessible by number) 2. Run my saved search for my bugs 3. Actual Results: The recent bug does not appear on the bug list Expected Results: The bugzilla software should have found the new bug, just as it finds 3 previous original bugs.
An additional comment is that at the bottom of the bug report and discussion, there's the bold entry BUG LIST First Last (this bug is not on your list) Show list Query page Enter new bug But the should be on my list. I just reported it. :-) The same thing is happening in this bug report.
Comment 2•20 years ago
|
||
"My bugs" skips UNCONFIRMED bugs. You can set up a named search including UNCONFIRMED bugs: - Bring up the original My Bugs list - Press "Edit Search" - Add UNCONFIRMED to list of allowed states - Press Search - Enter "My bugs, for real now" in the name field, then press "Remember Search" If you are an administrator, you can edit the mybugstemplate parameter to include UNCONFIRMED bugs.
Thanks, Mark. I had never noticed that before. Got them all listed now, including the duplicates.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•