Bug 1033172

Summary: "Change multiple bugs at once" form changes unwanted fields
Product: [Community] Bugzilla Reporter: Bill Nottingham <notting>
Component: Creating/Changing BugsAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED UPSTREAM QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: jmcdonal, rjoost, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 23:27:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bill Nottingham 2013-11-21 16:16:34 UTC 
Description of problem:

How to reproduce:
1) Set up a large number of bugs in 'change multiple bugs at once' (such as a few hundred)
2) Set them to only change one field
3) Hit submit
4) Eventually, you'll get a proxy error. You won't get a result page, but your change is still running in the background
5) Have someone else change unrelated fields in some of these bugs (assignee, status, resolution, etc.) before your change is run on the bug
6) Your change then resets whatever fields the other person has changed back to their state when you started your submission, without warning.

It's essentially the situation that required the mid-air collision warning, except it blindly overwrites things with no warning. And it's doubly problematic in that the situations where you'd want to use the 'change multiple bugs' page is where you're more likely to exacerbate it.

Version-Release number of selected component (if applicable):

bz-current
Comment 1 Simon Green 2013-11-21 23:27:25 UTC 
This is a known issue from upstream Bugzilla.