Closed
Bug 577956
Opened 14 years ago
Closed 14 years ago
Bugs which were never confirmed cannot be reopened as UNCONFIRMED
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 4.0
People
(Reporter: LpSolit, Assigned: LpSolit)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
812 bytes,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
Reproducable with a clean 4.0 installation: An UNCONFIRMED bug which is resolved cannot be reopened as UNCONFIRMED. This means that reporters with no privs cannot reopen their bug at all, because CONFIRMED and IN_PROGRESS are not available to them. When looking at the bug status workflow (editworkflow.cgi), no transition to UNCONFIRMED is allowed, as mentioned in my review in bug 486292 comment 37.
Flags: blocking4.0+
|
Assignee | |
Comment 1•14 years ago
|
||
mkanat, should we add RESOLVED/VERIFIED to UNCONFIRMED transitions back to STATUS_WORKFLOW in DB/Install.pm? Or do you have another idea in mind?
|
||
Comment 2•14 years ago
|
||
Hmm. Yeah, since the statuses are now named CONFIRMED and UNCONFIRMED instead of NEW and UNCONFIRMED, I think it will be clear what to do with a bug even though there are two possible open statuses to re-open it to. So we should add those transitions in, for sure.
|
|
Assignee | |
Comment 3•14 years ago
|
||
I didn't test it, but it only affects new installations, so there is no other places to fix, AFAIK.
Assignee: create-and-change → LpSolit
Status: NEW → ASSIGNED
Attachment #461951 -
Flags: review?(mkanat)
|
|
||
Updated•14 years ago
|
Attachment #461951 -
Flags: review?(mkanat) → review+
|
|
||
Updated•14 years ago
|
Flags: approval4.0+
Flags: approval+
|
|
Assignee | |
Comment 4•14 years ago
|
||
Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/ modified Bugzilla/Install.pm Committed revision 7412. Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/4.0/ modified Bugzilla/Install.pm Committed revision 7356.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•