Bug 847738

Summary: When query.cgi?product=$PRODUCT is acessed, load component list for $PRODUCT directly
Product: [Community] Bugzilla Reporter: David Jaša <djasa>
Component: Query/Bug ListAssignee: Simon Green <sgreen>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 4.2CC: ebaak
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-14 00:41:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Jaša 2012-08-13 11:49:12 UTC
Description of problem:
When query.cgi?product=${PRODUCT} is acessed, load component list for PRODUCT directly. There are two problems with this approach:
1. this is b/w-inefficient expecially for smaller products (TCMS, oVirt, ...)
2. it triggers firefox lockup mentioned in bug 823339

Version-Release number of selected component (if applicable):
bugzilla 4.2 on bugzilla.redhat.com as of 2012/08/13

How reproducible:
always

Steps to Reproduce:
1. go to bugzilla.redhat.com/query.cgi?product=oVirt
2.
3.
  
Actual results:
1. page loads full component list across all classifications and products
2. the component list is narrowed down by javascript

Expected results:
component lists is narrowed down server-side

Additional info:
Marking as a regression because previous bugzilla didn't suffer from this issue

Comment 1 David Jaša 2012-08-13 12:06:42 UTC
(In reply to comment #0)
...
> There are two problems with this approach:
> 1. this is b/w-inefficient expecially for smaller products (TCMS, oVirt, ...)
> 2. it triggers firefox lockup mentioned in bug 823339

3. it breaks "back" button function which is heavily used in bugzilla in general

Comment 2 Simon Green 2012-08-14 00:41:28 UTC

*** This bug has been marked as a duplicate of bug 823339 ***