Closed Bug 676416 Opened 13 years ago Closed 13 years ago

'Change Several Bugs at Once' won't change Products

Categories

(Bugzilla :: Bugzilla-General, defect)

Product:
Bugzilla
Component:
Bugzilla-General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 663208

People

(Reporter: jwiseheart, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110615151330

Steps to reproduce:

Our company wants to import 2,885 records from our old database, to test migration to Bugzilla. Once the final decision is made, and since records in our old database can be added, changed or deleted in the meantime, they will want to purge and re-add all the records before going live.

I tried to add a Product named 'DELETE', and use the 'Change Several Bugs at Once' option to change all products to the 'DELETE' product (yes, I changed the allowbugdeletion setting to ON). I never got to the step where I delete the 'DELETE' product.


Actual results:

No Product changes occurred. This leaves me with the task of manually changing 2,885 bugs to the DELETE product.


Expected results:

I was hoping all 2,885 bugs would have their Product setting change to the DELETE product, so I can purge them and re-populate from our XML import script.
I guess you are using Bugzilla 4.0.1?
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
I just tried updating multiple bugs for a single product. Although I was able to select the DELETE product, component, and version form the 'Change Several Bugs at Once' screen, click COMMIT, and it looks like it's working. 

But then, even though I already specified a component and version, it takes me to a 'Verify Version, Component' screen. I select the appropriate component and version again, but this time clicking COMMIT does nothing.

Sorry, I should have specified in the original post that it is this second 'Verify Version, Component' screen COMMIT button where I'm seeing the problem.
Version 4.0. Was this fixed in 4.0.1?
I just looked at bug 663208. Yes, this is a duplicate of that issue. I'll try the patch and see if that fixes it...
That fixed the problem, thank you!
You need to log in before you can comment on or make changes to this bug.