363867 - bugs_activity does not track duplicates table entries

Status: NEW

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Kevin Benton]

No attempt is currently being made to track duplicate bug markers in the bugs_activity table.  The dupe_of bug gets a longdescs entry that a bug has been marked as a dupe, however, that's not the case when a bug regresses to a REOPENED state.  That makes it more difficult to see when a bug regresses from being marked as a duplicate from the bug it was marked as a dupe of.  It seems to me that bugs_activity entries should be made in both the dupe and the dupe_of bug when a change is made to the duplicates table so that the change will show up in the activity log.

Dave Miller suggested that while implementing this, it would be possible in checksetup.pl to capture historic regression data and auto-populate the bugs_activity table.

Bill Barry suggested that a check be added to sanitycheck.cgi and I think it makes sense to make sure that stray entries are not present in the activity log (meaning those that are not possible knowing that a bug can not start out as a dupe).

I'm not sure if this should be considered just one bug or three separate bugs, but I'll leave that up to the people who choose to implement part or all of it. :)