Bug 1693111

Summary:	When changing products keep component and sub-component if they are valid on the new product
Product:	[Community] Bugzilla	Reporter:	Rony Gong 🔥 <qgong>
Component:	Creating/Changing Bugs	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jeff Fearn 🐞 <jfearn>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	agk, emmanuel, grgoffe, huiwang, hyu, jfearn, jmcdonal, khong, mtahir, qgong
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1272817	Environment:
Last Closed:	2022-05-09 00:14:59 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:
Bug Depends On:	1272817
Bug Blocks:

Description Rony Gong 🔥 2019-03-27 08:28:39 UTC

+++ 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

Comment 1 Rony Gong 🔥 2019-03-27 08:29:22 UTC

Currently, the subcomponent value got lost after select product from RHEL7 to RHEL6

Comment 2 Jeff Fearn 🐞 2019-03-27 08:37:40 UTC

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.

Comment 3 Rony Gong 🔥 2019-04-04 09:10:32 UTC

(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?

Comment 4 Jeff Fearn 🐞 2019-10-10 14:12:22 UTC

(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

Comment 6 Petr Pisar 2020-08-26 14:33:44 UTC

*** Bug 1872724 has been marked as a duplicate of this bug. ***

Comment 7 Emmanuel Seyman 2020-08-26 14:41:25 UTC

*** Bug 1872748 has been marked as a duplicate of this bug. ***

Comment 9 Jeff Fearn 🐞 2022-04-22 05:55:43 UTC

This works ... https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&component=Extensions&sub_component=RedHat

Comment 10 Jeff Fearn 🐞 2022-04-28 06:44:23 UTC

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.

Comment 11 Jeff Fearn 🐞 2022-05-05 00:10:46 UTC

The fix for this bug has been deployed to the stage server for public testing.

https://bugzilla.stage.redhat.com/

Comment 12 Jeff Fearn 🐞 2022-05-09 00:14:59 UTC

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.