marking a bug as duplicate has the effect of hiding any tasks that were uniquely on the duplicate

Bug #165110 reported by Emmet Hikory
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

When a bug has multiple bug tasks, and the bug is marked as a duplicate of a bug with a smaller number of tasks, the extra tasks are then unavailable for editing (as it is a duplicate), but not pushed to the duplicated bugs. As a result bug tasks become either lost or unavailable for update.

Observed Behaviour:
    A bug is opened, with a single bug task on a package
    Another bug is opened with bug tasks on two packages
    The second bug is marked as a duplicate of the first
    The tasks on the second bug become disabled due to duplication
    The first bug does not contain a task for the second package

Desired Behaviour:
    A bug is opened, with a single bug task on a package
    Another bug is opened with bug tasks on two packages
    The second bug is marked as a duplicate of the first
    The first bug's bug tasks are updated to include the second bug task from the second bug
    The tasks on the second bug become disabled due to duplication
    The first bug lists all tasks with status for all duplicates

Corollary desired behaviour:
    If a bug task is created due to duplication, and the duplication later removed, and there has been no update activity on the automatically created task, the automatic task should be removed from the original bug.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Probably this should be implemented at the same time as bug 30537.

Changed in malone:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Emmet Hikory (persia) wrote :

The subscriber merge portion of 30537 is already complete. I'm not opposed to waiting for the spec, but certainly won't complain if the individual portions of 30537 (including this) are completed separately as time allows.

Revision history for this message
Robert Collins (lifeless) wrote :

I think that this needs a prompt rather than automatic merging; its up to folk doing a merge to say which is the most representative bug, and to merge any metadata that isn't amenable to automatic merging. Given that bugtasks can't be deleted (at the moment) I hesitate to merge tasks.

summary: - When a bug is marked "Duplicate", all bug tasks should be preserved
+ When a bug is marked "Duplicate", tasks on projects/packages not in the
+ master are closed without notice
summary: - When a bug is marked "Duplicate", tasks on projects/packages not in the
- master are closed without notice
+ marking a bug as duplicate has the effect of hiding any tasks that were
+ uniquely on the duplicate
Changed in launchpad:
importance: Medium → Low
tags: added: duplicate-handling
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.