Red Hat Bugzilla – Bug 1157849
[RFE] Use AJAX for the component list when editing and searching bugs
Last modified: 2015-09-21 02:33:58 EDT
Description of problem:
When I want to reassign a Fedora bug, clicking on "Edit" for "Component" fails to give me the complete list of components because they are too many for a combobox:
* In QtWebKit (Konqueror+KWebKitPart, Rekonq), it only offers the first 9999 components (up to openstack-ceilometer in the alphabet) and the last one (zzuf), anything inbetween (e.g. xorg-x11-* packages) is not shown.
* KHTML (Konqueror+KHTML) fails to load the component list entirely, the combobox shows only the bug's current component, as if I had never clicked on "Edit".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a Fedora bug in Konqueror or Rekonq (or any other QtWebKit browser, I suppose).
2. Click "Edit" on "Component".
3. Try to select another component from the combobox.
Not all components are shown.
A solution to edit the component that does not rely on a combobox with more than 10000 entries.
Reportedly, Firefox does not have that limitation, but several browsers do.
This is a known problem that has been reported many times over the years and results from Fedora's insanely long component list, which is now > 17,000 components. The lengthy component list also causes performance problems and some users see timeouts when attempting to load some Bugzilla pages.
Most web browsers limit listboxes to 10,000 items to prevent malicious pages from causing the browser to run out of memory. This is not something that the Bugzilla maintainers can change -- we've already tried, and failed to convince the Chrome folks to increase the limit.
*** This bug has been marked as a duplicate of bug 787206 ***
Apologies, I was looking at enter_bug.cgi instead of show_bug.cgi. A similar solution to the one in enter_bug.cgi should be implemented in show_bug.cgi, and ideally for query.cgi (Advanced Search) as well.
*** Bug 1165747 has been marked as a duplicate of this bug. ***
Jeff has had some ideas on how to make the drop down box easier to use than what we currently have in enter_bug.cgi.
The fix for this bug may also fix one or more of the following bugs:
* Bug 1132442
* Bug 1136681
* Bug 1136687
* Bug 1136693
* Bug 1151025
* Bug 1153422
* Bug 1180018
* Bug 1181004 (probably onlt partially)
QA environment(bzweb01-qe) with version(4.4.9033-1, DB: mysql)
QA environment(bzperfweb01.app.qa) with version(4.4.9033-1, DB: psql )
Result: Failed, the assingee, qa_contact, cc, docs_contact doesn't changed when component changed.
1.create a bug of RHEL7, select 'aic94xx-firmware' as component
2.Then update above bug's component to '389-ds-base',save
3. Check the assingee, qa_contact, cc, docs_contact, no change.
The default assingee, qa_contact, cc, docs_contact of 'aic94xx-firmware' and '389-ds-base' are not same.
Another error happened in advanced search:
1.Go to advanced page,
2.Select 2 products by press the "Ctrl" button
Then page pop up dialog contains below message:
Error: Bad product id: v90_product,v97_product at /loader/0x7f199b1ce098/Bugzilla/Extension/ChosenAjax/WebService/Search.pm line 108
I found a regression on the Advanced Search page when not logged in. If you attempt to select a product, Bugzilla pops up an error dialog with the message "Error: You must log in before using this part of Red Hat Bugzilla."
Suggest extending the QE test cases to include using the search fuinctionality while not logged in. Of course, this should only show public bugs and fields, similar to seatching as a logged in user who has no groups.
Thanks, QE will add this case. Also test the search by a user who has no groups, it works fine.
Why add an abandoned commit 48177, please confirm it.
QA environment(bzweb01-qe) with version(4.4.9033-5, DB: mysql)
QA environment(bzperfweb01.app.qa) with version(4.4.9033-5, DB: psql )
This is now on our testing site at https://partner-bugzilla.redhat.com/
Please test it out and provide feedback.
*** Bug 1254423 has been marked as a duplicate of this bug. ***
(In reply to Matt Tyson from comment #16)
> This is now on our testing site at https://partner-bugzilla.redhat.com/
> Please test it out and provide feedback.
+1 for the new interface
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.