Bug #7809 empty severity field

Submitted: 11 Jan 2005 16:09 Modified: 21 Jan 2005 6:00
Reporter: Martin Friebe (Gold Quality Contributor) (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Websites: bugs.mysql.com Severity:S3 (Non-critical)
Version: OS:
Assigned to: Dean Ellis CPU Architecture:Any

[11 Jan 2005 16:09] Martin Friebe
Description:
several bugs on this page #7788 #7786 #7776 #7774 show an em,pty severity in search results and/or bugview page.

according to my observation, this happens, if the originator/or a developer changed the severity

In order to test this bug, I will have to report one, so I will test on this bug (as I do not like to alter other bugs for no reason related to them)

How to repeat:
report a bug

change its severity

Suggested fix:
ensure severity is displayed / stored
[11 Jan 2005 16:10] Martin Friebe
making it a feature request, in order to verify the bug
[11 Jan 2005 16:12] Martin Friebe
well, the above description does not seem to apply, at least not, if the reporter changes severity.

since severity seems a required fields, the bugs listed in the bug description are still showing starnge behaviour.
[14 Jan 2005 16:48] Martin Friebe
just seen again:
bug 7708 had a severity of "non critical", then it was verified, with the following changes mailed to me:

 ID:          7708
 Updated by:  Victoria Reznichenko
 Reported by: Martin Friebe
 User Type:   User
-Status:      Open
+Status:      Verified
-Priority:    
+Priority:    Low
 Severity:    Non-critical
 Category:    bugs.mysql.com

now severity is showing empty

##
it might be at random 7688 was not yet modified since I reported it, the report confirmation mail contained severite "non critical", but if I list it now via www, severity is empty
[21 Jan 2005 6:00] Dean Ellis
Martin, this should be fixed now.  Let us know if you see the problem again.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.