Red Hat Bugzilla – Bug 1272817
[Usability] When changing products, don't clear other fields if their values are still valid for the new product
Last modified: 2015-12-15 21:13:54 EST
Description of problem:
When changing the Product on a bug, the Component and Subcomponent 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 Subcomponent.
Version-Release number of selected component (if applicable):
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 subcomponent it started with.
After step 2, the Component field is cleared and the Subcomponent field vanishes.
The best time I could manage for Steps 2 and 3 was 24 seconds.
When changing a bug from RHEL6 to RHEL7, only the fields that aren't still valid for RHEL7 get cleared.
No, this should be fixed for 4.4. It is a direct consequence of the recent BZ upgrade and is causing our users significant frustration.
Removing dep as I believe we can change this without impacting the work Hao is doing.
Verified this issue.
The result is PASS
1. Choose one bug of RHEL7
2. Edit the bug and change the bug's product RHEL6/RHEL5
3. Result: if RHEL6 and RHEL5 have the same component and subcomponent, the component and subcomponent are not cleared in the field
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.