Closed
Bug 58552
Opened 24 years ago
Closed 22 years ago
[RFE]MISSING should be added to the choice of resolution
Categories
(Bugzilla :: Bugzilla-General, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tarahim, Assigned: CodeMachine)
References
Details
When some bug is dependent on certain URL, and the URL is changed before the bug
is analyzed, it is currently resolved as Invalid. However, resolving Invalid
puts the bug completely out of radar screen while the bug may be lurking
somewhere. Therefore, in order to keep some degree of awareness to the possible
existence of the bug, I suggest to add Missing as a status to resolve when such
change at URL has definitely made the bug uncatchable. Just my $0.02.
Comment 1•24 years ago
|
||
Clearing platform:Mac from a Webtools bug
OS: Mac System 9.x → other
Hardware: Macintosh → Other
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → Bugzilla 2.16
Comment 2•23 years ago
|
||
-> Bugzilla product, General component (request for new status), reassigning.
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Comment 3•23 years ago
|
||
This is covered by the work on defining your own statuses.
Gerv
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 5•23 years ago
|
||
Wouldn't this just be part of the custom resolutions thing?
QA Contact: matty → jake
Assignee | ||
Updated•23 years ago
|
Depends on: bz-custres
Comment 6•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 7•22 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Comment 8•22 years ago
|
||
Correcting summary; it's about resolution, not status (I searched for bugs
having to do with resolutions and missed that).
By the way, doesn't this case fit nice into WORKSFORME? Even if it doesn't, the
proposed resolution would be highly Mozilla-specific, thus it should only be
implemented by way of custom resolutions (bug 94534). I'd mark this bug WONTFIX.
Summary: [RFE]Resolved Missing should be added to the choice of status. → [RFE]MISSING should be added to the choice of resolution
Comment 9•22 years ago
|
||
yeah, I agree. bug 94534 is the way to do this, implementation wise. If you
want this specifically for mozilla.org, please reopen and change the product to
mozilla.org, component Bugzilla Components/Keywords, and leave the dependency.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 10•22 years ago
|
||
clearing milestone in WONTFIX/WORKSFORME/INVALID so it'll show up as untriaged
if it gets reopened.
Target Milestone: Bugzilla 2.18 → ---
Updated•12 years ago
|
QA Contact: jake → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•