Updates in Bugs_Activity don't include duplicate markers

[David Miller]

Kevin Benton wrote on 12/13/06 5:31 PM:
> I'm trying to figure out the decision behind not including state changes 
> to the duplicates table in the bugs_activity logs.  Anyone here able to 
> help?
> 
> Till I looked at the code, I thought that all changes to bugs past 
> creation (except comments and attachments) were supposed to be logged in 
> bugs_activity so that the full history of a bug could be determined.  
> Was that an oops or should I file a bug on that?

Some history of how duplicates were handled might be in order to help 
explain it. :)

Originally, *nothing* was done about duplicates except to add a comment 
to the bugs saying so.  Creating the duplicates table was done later to 
make it easier to automate statistics type stuff (it's really hard to 
scan comments looking for duplicate indicators, and more so now that 
we've localized them).

> What I'm thinking is that there needs to be a set of activity entries 
> against both bugs detailing these issues.  What do others think before I 
> get serious and file a bug on this?

Sounds like a good idea to me.  field names could be "dupe of" on the 
duplicate bug's activity table and I'm not sure what to use (just 
"duplicate" maybe?) on the remaining master bug.

It may be possible to back-date to the beginning of time in the activity 
table by scanning for resolution=DUPLICATE changes and looking for 
comments that happened at the same time on the affected bugs.

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/