+++ This bug was initially created as a clone of Bug #1272817 +++ Description of problem: When changing the Product on a bug, the Component and Sub-component fields get cleared. This wastes time for users who are moving bugs between products that have similar (and large) component lists (e.g. RHEL 5, 6 and 7). That is quite a common use-case for RHEL PM's and engineers. If a user moves a bug to a product where the Component is still valid, the Component should remain and the user should not be forced to make another selection. The same should be true for the Sub-component. Version-Release number of selected component (if applicable): 4.4.9039 How reproducible: Always Steps to Reproduce: 1. Choose a bug from https://bugzilla.redhat.com/buglist.cgi?classification=Red%20Hat&component=kernel&product=Red%20Hat%20Enterprise%20Linux%206&rh_sub_components=File%20Systems%20Other 2. Change the product to Red Hat Enterprise Linux 7 3. Measure how long it takes you to put the bug back in the same Component and sub-component it started with. Actual results: After step 2, the Component field is cleared and the Sub-component field vanishes. Expected results: When changing a bug from RHEL6 to RHEL7, only the fields that aren't still valid for RHEL7 get cleared. Additional info: none
Currently, the subcomponent value got lost after select product from RHEL7 to RHEL6
I think this is a more general problem, it's not possible to set the sub-component in any URL and so the clone is just another example of this.
(In reply to Jeff Fearn 🐞 from comment #2) > I think this is a more general problem, it's not possible to set the > sub-component in any URL and so the clone is just another example of this. Do we plan to support the field subcomponent for this feature?
(In reply to Rony Gong 🔥 from comment #3) > (In reply to Jeff Fearn 🐞 from comment #2) > > I think this is a more general problem, it's not possible to set the > > sub-component in any URL and so the clone is just another example of this. > > Do we plan to support the field subcomponent for this feature? Yeah I think we should, we probably need to fix subcomponents not being settable in a URI first though. e.g. This doesn't set sub-component https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&component=Extensions&rh_sub_component=RedHat
*** Bug 1872724 has been marked as a duplicate of this bug. ***
*** Bug 1872748 has been marked as a duplicate of this bug. ***
This works ... https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&component=Extensions&sub_component=RedHat
On QA server. 1: Find, or create, a RHEL-8 kernel bug. 2: Change the product to RHEL-7. Component, sub-component, target milestone are all kept. Version and target release are also kept, but are now red and bold highlighting they are not valid for the new product. 3: Change version and target release 4: Submit changes Bug changes are applied without intermediate change page. 5: Now change product to Bugzilla Component and sub-component are unset. Other fields are either unset or marked as invalid.
The fix for this bug has been deployed to the stage server for public testing. https://bugzilla.stage.redhat.com/
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.