Entry tags:
more bugzilla tweaking
People may have noticed that the Bugzilla form has simplifed again! i went through and disabled all the fields we aren't using that Bugzilla would let me disable, and simplified the ones that couldn't.
* Fields no longer visible: Target Milestone and QA Contact, since we aren't using them
* Flags no longer visible: blocking-launch (we've passed launch) and Upstream
* "Version" is a required field, but I removed 0.1 and 0.5 under the DW Development product, leaving only 1.0 and Unspecified. (I'd disable 1.0 and make it just be Unspecified, but that'd require a lot of bug editing, since bugs are about 50/50 split between the two. Still, don't worry about it when opening a bug.)
* Fields no longer visible: Target Milestone and QA Contact, since we aren't using them
* Flags no longer visible: blocking-launch (we've passed launch) and Upstream
* "Version" is a required field, but I removed 0.1 and 0.5 under the DW Development product, leaving only 1.0 and Unspecified. (I'd disable 1.0 and make it just be Unspecified, but that'd require a lot of bug editing, since bugs are about 50/50 split between the two. Still, don't worry about it when opening a bug.)

no subject
Does Bugzilla not store its items in an SQL database that you have access to?
Then I expect one mass UPDATE would be enough to fix it ("UPDATE bugs SET version = 'Unspecified' WHERE version = '1.0'", in pseudocode).
no subject