User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24 Build Identifier: Bugzilla 4.0 I have tried this on a private server and landfill. It would seem if you attempt to move multiple bugs to another product the "Verify version" page will never accept your selections Reproducible: Always Steps to Reproduce: 1. Get a buglist of at least 2 bugs. 2. Use Change multiple bugs at once. 3. Select 2 bugs. 4. Change their product from their current. 5. At "Verify version" page select proper information 6. Click commit Actual Results: The "Verify version" page will reload asking for the same information again. Interesting note: the "Verify Bug Group" will disappear on the second render. Expected Results: The Commit button should should process bug activity for selected bugs. Move a single bug works fine from both the bug page and selecting only one bug with "Change several bugs at once".
I can reproduce in both 4.0.1 and 4.1.2. Didn't test with 3.6.5 yet.
3.6.5 is not affected.
Created attachment 538615 [details] [diff] [review] patch, v1 We have to copy the hash to not alter data used for subsequent bugs when calling set_all() in a loop in process_bug.cgi. The problem here was that some fields, including the component, version and target milestone, were deleted when calling set_all(), and so the subsequent bugs in a mass-change had no values for these fields, triggering the confirmation page again and again.
Comment on attachment 538615 [details] [diff] [review] patch, v1 Looks good to me. :-)
Committing to: bzr+ssh://firstname.lastname@example.org/bugzilla/trunk/ modified Bugzilla/Bug.pm Committed revision 7836. Committing to: bzr+ssh://email@example.com/bugzilla/4.0/ modified Bugzilla/Bug.pm Committed revision 7603.
I applied this patch on my clean 4.0.1 installation, and the problem still remains. (confirm page keeps coming up) Does it depend on other fixes since 4.0.1 stable?
(In reply to comment #6) > I applied this patch on my clean 4.0.1 installation, and the problem still > remains. (confirm page keeps coming up) > Does it depend on other fixes since 4.0.1 stable? D'Oh. The confirm page had unselected fields, so it kept repeating. Works fine if I actually select a value for those fields.
(In reply to comment #7) > D'Oh. The confirm page had unselected fields, so it kept repeating. Works > fine if I actually select a value for those fields. You're welcome to file a bug for the fact that it can be hard to notice that, and that we should validate it with JS.