Using a 5.0 on a Macintosh to bring up my bug list I am missing three bugs that are normally there using 4.x or 5.0 on Windows. This is very strange since I would guess that the client has very little to do with the query. The URL is: http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=hangas&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_d&order=bugs.target_milestone and it currently shows me 80 bugs on 4.7 Mac and 5.0 Windows, but only 77 bugs on 5.0 Mac. As a dogfood user I am concerned about this. I repeated this same problem with sspitzer replacing my name in the query, in this case one bug was missing. I repeated this problem on pmock's Mac and Windows builds of 5.0.
paulmac - who would this belong to? Thanks :-)
I can't figure this out at all. cc'ing terry to see if he knows what could be happening on the bugzilla server side. Giving to pollmann, to see if he has any ideas, or knows where this bug might belong.
Could you please compare the buglists and figure out which bug numbers are missing?
bugs 5333 5648 and 5656 are missing, they are all P4 if that matters
They are all imported from bugzilla, probably has something to do with it
s/bugzilla/bugsplat/ ? Could this have to do with requiring a login first so that the appropriate cookie gets set?
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
Yes. That's the problem. In bugspat, if a bug is marked 'Only people in the "Netscape Confidential" group can see this bug', and you are not logged in, you won't see it in queries. To see such bugs, all you need to do is log in. To log in, try to visit one of the restricted bugs: http://bugzilla.mozilla.org/show_bug.cgi?id=5648 You'll get: Permission denied. blah blah blah _log in_. Click on the _log in_ link. Enter your bugzilla username and password. Run the query again. The reason that this worked on Win for you is that you logged in on that machine before (possibly even that build) and had a cookies.txt file lying around that already had your email/password in it. Marking this bug invalid.
thanks for the investigation, eric, excellent sleuthing :-)
You need to log in before you can comment on or make changes to this bug.