Bug #5166 "Assigned" state of the bug is inconsistent with actions history.
Submitted: 23 Aug 2004 12:34 Modified: 15 Dec 2005 18:35
Reporter: Sergey Petrunya Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Websites: bugs.mysql.com Severity:S2 (Serious)
Version: OS:
Assigned to: CPU Architecture:Any

[23 Aug 2004 12:34] Sergey Petrunya 
Description:
"Assigned" field state of the bug is inconsistent with actions history

How to repeat:
Visit this url:
https://bugs.mysql.com/search.php?cmd=display&bug_type=Any&status=Verified&bug_age=0&order...

See the first bug is bug#5138, and it is not assigned to anyone ("Assigned" field is blank).

Then click on the bug number, and get to 
 https://bugs.mysql.com/bug.php?id=5138
Again there is no "Assigned" field, and the bug looks like unassigned.

Then click on "View progress log" and see that the only modification to "assigned" field was:
-Assigned to:      
+Assigned to:      mlord@mysql.com

which is not consistent with current "unassigned" bug state.
[15 Dec 2005 18:35] Jim Winstead 
Changes to the Assigned field are logged properly now.