Bug 47073 - bugzilla gets confused by bugs with initally empty descriptions
Summary: bugzilla gets confused by bugs with initally empty descriptions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.18
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-03 00:13 UTC by Jeremy Katz
Modified: 2013-06-24 03:08 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-28 20:16:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeremy Katz 2001-07-03 00:13:23 UTC
bugzilla gets a bit confused as to who added what comments to a bug if a
bug is initially entered with a blank description.  quite easy to reproduce
-- file a bug with a blank description field, then edit the bug to add a
comment and watch as the comment shows up as being given by the person
filing the bug.  example is bug 47002

Comment 1 David Lawrence 2001-07-05 03:15:02 UTC
Each comment is stored in a separate row in the database. Bugzilla assumes the
very first comment (date wise) is the one made by the reporter. If the reporter
does not enter anything then the next comment gets pushed up to the top even if
it was made by someone else. The proper way to fix this problem I think is to
just make it mandatory that a description is entered. I thought this was the
case but now I am not so sure. I will look through the code and make the
necessary changes.

Comment 2 David Lawrence 2006-04-08 17:48:10 UTC
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 3 David Lawrence 2008-08-28 20:16:44 UTC
Bugzilla 3.2 does not shift the the next comment up if the description is empty. So closing this as currentrelease.


Note You need to log in before you can comment on or make changes to this bug.