Open
Bug 92594
Opened 23 years ago
Updated 1 month ago
Moving an UNCONFIRMED bug's product needs to check whether product uses UNCONFIRMED.
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P3)
Tracking
()
NEW
People
(Reporter: CodeMachine, Unassigned)
References
()
Details
Attachments
(1 obsolete file)
See the activity of bug #92441. When the bug was moved to Webtools, it didn't get automatically confirmed. It was later confirmed by another person. Because Webtools requires a count of 0 votes to confirm a bug, all bugs in Webtools should be confirmed. When a bug's product is moved, all the votes get removed automatically, but products with zero count can still cause a confirmation, and this should be checked. I suggest that you do a full popular vote check here rather than simply checking whether the product has a zero vote count, in case bug #92593 is fixed.
Reporter | ||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Comment 1•23 years ago
|
||
->New (old by now?) product Bugzilla
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.10 → 2.10
Comment 2•23 years ago
|
||
This should also work the opposite way... if a bug is filed in Bugzilla and then moved to Browser, it should become UNCONFIRMED.
Reporter | ||
Comment 3•23 years ago
|
||
That sounds reasonable ... everconfirmed should be set to 0 and rechecked. I'm not sure how this would affect customised resolutions though, because AFAIK there's no current way in Bugzilla to unconfirm a bug.
Comment 4•23 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 5•21 years ago
|
||
OK, we probably ought to start moving on this so b.m.o can pick it up in the upgrade in the next couple weeks. We apparently have people abusing this to get their bugs automatically confirmed now by filing them in a product that doesn't use UNCONFIRMED (mozilla.org in particular), relying on someone to move the bug to the correct product for them. Here's what I think would be the easiest way to implement this: 1) If the bug is filed in a product that doesn't use UNCONFIRMED, everconfirmed needs to not ever be set. (maybe set it when the bug is ASSIGNED, since setting a bug to ASSIGNED confirms a bug anyway) 2) Any time a bug is reopened or moved between products, the UNCONFIRMED / NEW / REOPENED state needs to be set based on that product's rules and the everconfirmed value.
Comment 6•20 years ago
|
||
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 7•19 years ago
|
||
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
Comment 8•19 years ago
|
||
*** Bug 227167 has been marked as a duplicate of this bug. ***
Testing <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=94534">links</a> within the comment field.
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•18 years ago
|
Assignee: myk → create-and-change
Comment hidden (spam) |
Updated•1 month ago
|
Attachment #9383537 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•