Closed
Bug 292975
Opened 20 years ago
Closed 20 years ago
severity of new bug is becomes "NEW" instead of "UNCONFIRMED".
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: bugzilla.admin, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Build Identifier:
Once i log a bug the severity of bug should be "UNCONFIRMED" it means that new
bug is added to the database but processing is not happens on this bug.Instead
of UNCONFIRMED state it defaultly set to NEW.Even i check in bugs table of
bug_sevrity ,where default field is set to "UNCONFIRMED" only.
Reproducible: Always
Steps to Reproduce:
1.Click New hyper link select product.
2.Log a bug.
3.after logging this bug check out in edit.html file it showes bug severity
as "NEW".
Actual Results:
newly logged bus severity is "NEW"
Expected Results:
newly logged bus severity should be "UNCONFIRMED".
Comment 1•20 years ago
|
||
"NEW" and "UNCONFIRMED" aren't severities, they are statuses.
You probably just need to enable the unconfirmed state in the Params.
If you need support, please use the resources at
http://www.bugzilla.org/support/ -- Bugzilla is not a support forum.
![]() |
||
Comment 2•20 years ago
|
||
I create new bugs every day using the latest CVS version and I never observed
this problem.
To enable the use of the UNCONFIRMED state, you have to change the "Number of
votes a bug in this product needs to automatically get out of the UNCONFIRMED
state" to a non zero value in editproducts.cgi.
mkanat, FYI there is no option in params to turn this on or off. ;)
Severity: blocker → normal
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•