Bug 1023590

Summary: Can't specify component anymore for Fedora
Product: [Community] Bugzilla Reporter: James Antill <james.antill>
Component: User InterfaceAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED DUPLICATE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: james.antill, jmcdonal, rjoost
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-18 01:15:24 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 James Antill 2013-10-25 20:43:26 UTC 
Description of problem:

 If you use JS and goto a URL like:

 https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=yum&version=rawhide

...the new magic component box is still blank, instead of being prefilled with yum.
Comment 1 Jason McDonald 2013-10-28 00:01:50 UTC 
You should see the following hint text under the Component box: "(Start typing a name, and a drop down box will be shown. You can hover over the component name for a description.)"

I just tested this again using Firefox 23 and the behaviour was as expected. When I type "yum" in the Component box, a drop-down list appears and is dynamically populated with al lthe components containing "yum" as a substring -- "yum" itself is the second last one in the list.  When I hover the mouse over "yum" the borwser show the hint "RPM installer/updater".

Are you seeing something different?
Comment 2 Jason McDonald 2013-11-18 01:15:24 UTC 
Please ignore my previous comment. For some reason I misread the report as being about entering a componet rahter than specifying one in the URL.

This bug actually appears to be a duplicate of Bug 1016162, which was fixed in RH Bugzilla 4.4.1010, released on November 3, 2013.

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