Closed Bug 23196 Opened 25 years ago Closed 25 years ago

[DOGFOOD]TM and QAC fields missing in bug descriptions

Categories

(Bugzilla :: Bugzilla-General, defect, P2)

x86
Linux
defect

Tracking

()

VERIFIED FIXED
Bugzilla old

People

(Reporter: dbaron, Assigned: terry)

Details

Right now I'm not seeing any Target Milestone or QA Contact fields in bugs shown in bugzilla. I just submitted changes to a bug, and I got the following diffs. These fields are being lost. Is this just me or are others seeing this? From nobody@mozilla.org Wed Jan 5 20:09:43 2000 Date: Wed, 5 Jan 2000 17:09:41 -0800 (PST) From: bugzilla-daemon@mozilla.org To: warren@netscape.com, dbaron@fas.harvard.edu Cc: mscott@netscape.com, lchiang@netscape.com Subject: [Bug 22166] Changed - CPU Usage spikes after sending message http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=22166 *** shadow/22166 Wed Jan 5 16:50:59 2000 --- shadow/22166.tmp.22895 Wed Jan 5 17:09:40 2000 *************** *** 10,17 **** Component: Networking-Mail AssignedTo: warren@netscape.com ReportedBy: dbaron@fas.harvard.edu - QAContact: esther@netscape.com - TargetMilestone: M13 URL: Cc: mscott@netscape.com, lchiang@netscape.com Summary: CPU Usage spikes after sending message --- 10,15 ---- *************** *** 55,57 **** --- 53,58 ---- ------- Additional Comments From warren@netscape.com 2000-01-05 16:50 ------- I can't reproduce this, and the stack traces don't give me any clues. They just seem like random snapshots of normal activity. + + ------- Additional Comments From dbaron@fas.harvard.edu 2000-01-05 17:09 ------- + I'm still seeing this on the opt build 2000-01-04-09-M13 (Linux mozilla).
Actually, I don't think the data are being lost, since the changes didn't show up in view-bug-activity. I guess seeing this in the diffs just means bugzilla has stopped caring about these fields and is no longer including them in the text printouts it uses to make the diffs. However, this is still a serious problem.
Thanks. terry is fixing
Status: NEW → ASSIGNED
I accidentally blew away a critical bugzilla file. I have mostly restored it, and things should generally work. Leaving this bug open until I have fully restored everything.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Through the miracle of backups, the file in question has been completely restored.
per Terry, auto-verifying any resolved bug that hasn't been touched since before 2.10 was released.
Status: RESOLVED → VERIFIED
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: matty
Target Milestone: --- → Bugzilla old
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.