Bug 683642

Summary:	Mass change between products quite dangerous
Product:	[Community] Bugzilla	Reporter:	Ondrej Vasik <ovasik>
Component:	Creating/Changing Bugs	Assignee:	Simon Green <sgreen>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	ebaak
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-07 12:37:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ondrej Vasik 2011-03-09 22:26:01 UTC

Description of problem:
I had to change ~130 bugzillas from RHEL-5 to Fedora Rawhide - as we discussed with reporter that such things should be done there. I thought that feature "Change several bugs at once" will be the best option for it. It was not.
Everything went smoothly, no error, no message - and after query was processed, every single bugzilla was changed to ecryptfs-tools component - the component of the first one bugzilla in the mass change list. 
Of course, I have selected option "Do not change" in Component field - left as default.

How reproducible:
I tried just once, but I guess always


Steps to Reproduce:
1. Select several bugs from various components and try to move them to other product via "Change several bugs at once" way.
  
Actual results:
All bugs have the same component - of the first bugzilla in the list.

Expected results:
Components are not changed.

Additional info: It would be really good to have some way how to revert such changes ... changing it back manually is not the best experience...

Comment 1 Jeff Fearn 🐞 2012-05-30 04:41:37 UTC

As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.

Comment 2 Ondrej Vasik 2012-05-30 06:11:27 UTC

I haven't checked that recently - as consequences of this issue are quite time costly and causes spam. I'll probably give it a try on test instance of the bugzilla when time allows, still giving 7 days to reporter when noone manually responded for 1 year seems to be a bit unfair to me ;).

Comment 3 Jeff Fearn 🐞 2012-06-21 03:53:49 UTC

These bugs have been flagged as still relevant and are being reset to default values for PM consideration.

Comment 4 Simon Green 2012-09-07 12:37:25 UTC

I understand that this did not work as expected, but on the second page, a component was selected. There isn't an option to not change the component (or version) when changing products.

The only practical solution I can think of is not allowing product changes if the selected bugs have many components would cause more problems (when this behaviour is desired) than it would solve.

   -- simon

Comment 5 Ondrej Vasik 2012-09-11 13:43:30 UTC

I understand - the components could be different between products and you might not be able to find one in the other product. However, still I would expect some warning that not changing component is not possible or something like that (if some preview of changes or revert changes RFE is not possible). Bugzilla simply did something I haven't expected (and I have heard about other such cases, even though in most cases these were much less painful than my 2 hours reverting exercise).