Bug 1033172 - "Change multiple bugs at once" form changes unwanted fields
"Change multiple bugs at once" form changes unwanted fields
Status: CLOSED UPSTREAM
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs (Show other bugs)
4.4
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-21 11:16 EST by Bill Nottingham
Modified: 2014-03-16 23:34 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-21 18:27:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Mozilla Foundation 89822 None None None Never

  None (edit)
Description Bill Nottingham 2013-11-21 11:16:34 EST
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 18:27:25 EST
This is a known issue from upstream Bugzilla.

Note You need to log in before you can comment on or make changes to this bug.