Description of problem: https://bugzilla.redhat.com/frontpage.cgi shows a variety of useful query results. For most of the result sets, the listing is preceded by a line of the form: 21 bugs found. (show list) (back to top) ....where the items in brackets are links. The first link is a Bugzilla query url, such as: https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&email1=myusername%40mydomain.com&emailqa_contact1=1&emailtype1=exact However, for two of the categories, the bug count and the first link is missing. The categories concerned are titled "Open Issues with Flags Requested of You" and "Open Issues with Flags You Have Requested". These categories should be consistent with the others in exposing the underlying query. Incidentally, two users have recently asked me for those queries, and I came to this page looking for them, only to be blocked by this bug. Version-Release number of selected component (if applicable): 4.4.0007 How reproducible: Always Steps to Reproduce: 1. Login into https://bugzilla.redhat.com/ 2. Click on the "Front Page" link 3. Scroll down to "Open Issues: You Are QA Contact" 4. Observe the text "0 bugs found. (show list) (back to top)" above the table. 5. Scroll down a little further to "Open Issues with Flags Requested of You" 6. Observe that only "(back to top)" link is shown. above the table Actual results: The two categories named above are missing the bug count and "show list" link. Expected results: All categories should show the bug count and "show list" link. Additional info: none.
(In reply to Jason McDonald from comment #0) > These categories should be consistent with the others in exposing the > underlying query. Incidentally, two users have recently asked me for those > queries, and I came to this page looking for them, only to be blocked by > this bug. There is no underlying query, so the link will be a hardcoded list of bug ids (similar to what is seen on the dependency tree page) -- simon
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. -- simon