Launchpad itself

Duplicate bug handling

Registered by Brad Bollenbach on 2005-09-15

Duplicate handling needs to be smarter in Launchpad than in other bug trackers because the same bug can be recorded as needing a fix in multiple places. For maximum efficiency, making and changing duplicate markings should be done using a form displayed on the duplicate bug report itself. Bugtasks and other information should be merged into the canonical bug report, but it should still be possible to undo a duplicate marking so as to return both bug reports to how they were previously.

Read the full specification

Blueprint information

Status:: Complete

Approver:: Steve Alexander

Priority:: Medium

Drafter:: Matthew Paul Thomas

Direction:: Approved

Assignee:: Björn Tillenius

Definition:: Obsolete

Series goal:: None

Implementation:: Unknown

Milestone target:: None

Completed by: Curtis Hovey on 2010-06-01

Related branches

Related bugs

Bug #3796: Display "Duplicate" as if it's a status	Triaged
Bug #29752: If a bug is marked as a duplicate, its subscribers should be notified when the duplicate bug changes	Fix Released
Bug #30537: marking a bug as duplicate 'loses' the tags the duplicate uniquely had	Triaged
Bug #52613: "Duplicate" system is conceptually erroneous	Won't Fix
Bug #111148: Mark a bug as being a bugtask of a more general bug	New
Bug #343110: +affectingbugs does not list bugs where a duplicate affects the user	Triaged

Sprints

Whiteboard

Needs Implementation section.

(?)

Work Items

This blueprint contains Public information

Everyone can see this information.

Subscribers

Daniel Hahler