Closed Bug 287207 Opened 20 years ago Closed 14 years ago

Add text of summary of bug marked as duplicate in each bug's comments

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: wsmwk, Unassigned)

References

Details

When marking duplicate, include text of summary field in each other's bug (the
dup and the one being duped). [similar to bug 125888]  Example:

in bug 24957

*** Bug 249372 been marked as a duplicate of this bug. ***
there are a large number of duplicate bugs but searching for: mybug, mybugs,
MyBugs etc doesn't turn them up

and in bug 249372

*** This bug has been marked as a duplicate of 24957 ***
include duplicates in search

In a small way this might improve duplicate searches, given that the key words
in summaries can differ between duplicates. Right now, the summary is provided
on a web page when one mouseover's the duplicate entry (above), but this isn't
in the bug text so it is not searchable. 

This, in part addresses the comments of Bug 24957#c33 "another way of dealing
with this would be to take the summaries of duplicate bugs, and attach their
extra words to the summary of the origional bug." - which seems at the moment
not trival to implement.

Recognize this isn't a perfect idea - a bug's summary may change in the future -
but it may provide some progress.
Severity: normal → enhancement
This is a reasonable step which adds minimal additional content to comments but
could have a significant positive impact on searches.
(In reply to comment #1)
> This is a reasonable step which adds minimal additional content to comments but
> could have a significant positive impact on searches.

+1

Excellent cost-benefit ratio: Really simple to implement, big improvement.
Whiteboard: good first bug
Hum, the idea itself is good, but we are planning to implement bug 200202 instead, which will make this bug obsolete.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Whiteboard: good first bug
You need to log in before you can comment on or make changes to this bug.