Closed
Bug 136631
Opened 22 years ago
Closed 22 years ago
Change to Invalid Option is Missing after Resolved Duplicate
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
People
(Reporter: mrmazda, Assigned: myk)
Details
When someone leaps ahead of the bug reporter to mark as dupe a bug that was not ready to submit but accidentally was submitted, the reporter should be able to change the accidental bug submission to invalid anyway, but this option is not present after resolved duplicate is applied. To provide the correct resolution of invalid one must reopen first before resolved invalid can be selected.
Comment 1•22 years ago
|
||
Same feature could be usefull to change status to WFM.
OS: OS/2 → All
Hardware: PC → All
Comment 2•22 years ago
|
||
Could you please explain how if you report a bug twice (even if once is accidental) one is not a dupe of the other? I seem to be missing your logic as to how one is invalid. By that logic, if one is invalid so then is the other one... Invalid is reserved when a reported bug is not really a bug. Eg, "Mozilla's javascript reports that 1+1 = 2. It should be 3" ...That said, this bug is just a duplicate of the bug to be able to change resolutions without reopening. (I can't find it though)
Reporter | ||
Comment 3•22 years ago
|
||
Where is Mozilla's definition of invalid? I don't seem to be able to locate it. To me, sequential bug numbers with similar or identical summaries from the same reporter means something went wrong, either user error or Bugzilla error. A dupe needs to be cross-referenced. Invalid does not.
Comment 4•22 years ago
|
||
It is common practice on b.m.o to resolve the second report of a double-submit as a duplicate of the first one. I don't think it's worth changing that. I think the reason for this practice is the principle that all resolutions need to be verified. So if there's a double-submit, and the second one is marked _invalid_ because of this, the verifier (who needs to be different from the resolver, at least that's best practice) needs to be able to verify that there's indeed another report for this issue. Thus the verifier of the second one needs the bug number of the first one, and that's what the _duplicate_ resolution provides (while the _invalid_ resolution does not). The definition of "INVALID" used on b.m.o can be found on http://www.mozilla.org/bugs : INVALID The problem described is not a bug, or not a bug in Mozilla. Or you can click on the "Resolution" link of any bug, which takes you to http://bugzilla.mozilla.org/bug_status.html Btw, I don't think this is an important issue :-)
Comment 5•22 years ago
|
||
I agree it should actually be marked as a DUPE, but the funtionality requested is a dupe. *** This bug has been marked as a duplicate of 92515 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•