If a bug is a duplicate from other one, its status should change

Bug #55730 reported by Alexandre Otto Strube
2
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

Explaining by example:

- Set bug A as being a duplicate from B
- Bug A is "confirmed"
- Set B as "Fix released"
- Bug A (which is a duplicate of B, was fixed also) is still stated as "Confirmed"

What would be the correct behavior:

- The current status to change from "confirmed" to "confirmed duplicate" - you always looks first to the orange status line than to the yellow duplicate above, ok

- Make the bug A status point to bug B status, as they are the same?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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