Bug 477924

Summary:	package selection dropdown urgently needs redesign
Product:	[Fedora] Fedora	Reporter:	John Mellor <john.mellor>
Component:	bugzilla	Assignee:	Itamar Reis Peixoto <itamar>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	cje, emmanuel, john
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-01 04:09:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Mellor 2008-12-25 14:51:36 UTC

Description of problem:
It is REALLY painful to select the proper component to report a bug on.  A ~10-line dropdown to select from many thousand components is inappropriate.  Scrolling is so difficult as to be near-unusable.

Version-Release number of selected component (if applicable):
version 3.1.4+

How reproducible:
every time

Steps to Reproduce:
1.use https://bugzilla.redhat.com/
2.note difficulty in selecting package
  
Actual results:
selecting the correct product is very well done.  Selecting the package or component is extraordinarily difficult.

Expected results:
a much better selection mechanism

Additional info:

Comment 1 Emmanuel Seyman 2009-01-05 09:17:59 UTC

This should be filed against the Bugzilla product and the Creating/Changing Bugs component and not the bugzilla component of Fedora 10.

Can anyone change this ?

Comment 2 Fedora Admin XMLRPC Client 2009-02-11 19:25:21 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 cje 2009-02-20 01:32:46 UTC

i think this bug needs to be moved to _product_ 'Bugzilla' (which is in
classification "other").

Comment 4 Itamar Reis Peixoto 2009-03-01 04:09:15 UTC


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