Closed
Bug 266297
Opened 20 years ago
Closed 17 years ago
Can't change NEW bug back to UNCONFIRMED
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
FIXED
Bugzilla 3.2
People
(Reporter: eyalroz1, Assigned: LpSolit)
References
Details
(Whiteboard: [blocker will fix])
I have editbugs in bugzilla.mozilla.org, and I just submitted a bug which on
first thought seemed well-enough confirmed, but after looking at it again I want
to make it UNCONFIRMED. But I can't! My options are:
- Leave as NEW
- Accept bug (change status to ASSIGNED)
- Resolve bug, changing resolution to ___
- Resolve bug, mark it as duplicate of bug #___
- Reassign bug to ___
- Reassign bug to owner and QA contact of selected component
There should be an option to 'de-confirm' the bug.
Assignee | ||
Comment 1•20 years ago
|
||
If your bug is invalid, mark it as RESOLVED INVALID!
Reporter | ||
Comment 2•20 years ago
|
||
It's not invalid, it's just that I don't feel confident enough to call it
'confirmed' just because I have editbugs.
Comment 3•20 years ago
|
||
Confirmed ;-)
For what it's worth, I also have editbugs and frequently open bugs as
UNCONFIRMED instead of NEW. I can definitely see the need to drop a new bug to
the former state.
Prog.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Comment 4•20 years ago
|
||
(In reply to comment #1)
> If your bug is invalid, mark it as RESOLVED INVALID!
IMHO, and to echo what the reporter said, the INVALID / UNCONFIRMED / NEW
states might be described as:
1) RESOLVED INVALID = we believe this is not a valid bug
2) UNCONFIRMED = we do not know whether or not this is a valid bug
3) NEW/ASSIGNED/REOPENED (confirmed) = we believe this is a valid bug
It should be possible to transition freely between these states as appropriate
when further investigation is done and/or the available evidence changes.
I think that at present UNCONFIRMED -> (confirmed) is the ONLY change to a bug
that cannot be reversed through the bugzilla UI.
This cuts off the possibility of correcting a mistake if a bug is confirmed
when it should not have been.
Comment 5•19 years ago
|
||
*** Bug 312279 has been marked as a duplicate of this bug. ***
Comment 6•19 years ago
|
||
This would be useful, especially since for b.m.o, different products/components use the UNCO state differently. It would also help in situations where bugs are confirmed accidentally.
Updated•18 years ago
|
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Comment 7•18 years ago
|
||
*** Bug 362098 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 8•17 years ago
|
||
Now that you can customize your workflow, see bug 101179, you are free to enable the NEW -> UNCO transition if you want to.
Assignee: create-and-change → LpSolit
Severity: normal → enhancement
Depends on: bz-custstat
Whiteboard: [blocker will fix]
Target Milestone: --- → Bugzilla 3.2
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•