Bug 163102

Summary: Bulk reassign bugs should change component if product reassignment selected
Product: [Community] Bugzilla Reporter: Paul W. Frields <stickster>
Component: Bugzilla GeneralAssignee: David Lawrence <dkl>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.18Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://bugzilla.redhat.com/bugzilla/
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-19 17:38:10 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 Paul W. Frields 2005-07-12 21:41:26 UTC
Description of problem:
I would like to be able to select several bugs for a new Product and Component
at the same time.  If I select a new Product for reassignment, the Component
list stays hooked to the bugs' current Product.

Version-Release number of selected component (if applicable):
2.18

How reproducible:
Every time, I think... I only have access to fedora-docs bugs as an FDP maintainer.

Steps to Reproduce:
1. Get bug list (in my case, all fedora-docs bugs), select "Change Several Bugs
at Once" from footer menu.
2. Select some bugs, and choose a new Product (Fedora Documentation) from the
dropdown for reassignment.
  
Actual results:
The Component list is still from the bugs' existing Product (Fedora Core).


Expected results:
The Component list should change so I can put the bugs in a Component that makes
sense for the new Product.

Additional info:

Comment 1 Paul W. Frields 2005-07-19 17:38:10 UTC
I see that I am, in fact, "a ass," and that BZ asks me to fill these in on the
next page (which I didn't see since I wasn't truly making a change).  I suppose
this enhancement could still be useful, but it now seems trivial and petty in
the face of the excellent BZ programmers' workload.  Sorry to "bug" you.  ("Gee,
we never heard *that one* before. <sigh/>")