Wishlist: Does not manage chains of duplicate reports

Usage case:

LP user marks bug A as dup of bug B, since both describe an identical situation with identical symptoms.

LP user later marks bug B (the "semi-master report") as a duplicate of the general case bug G, which doesn't list the exact identical same symptoms, but seems to correctly identify the root cause of the problem. This is currently NOT possible.

Currently, the user must first un-dupe bug A, before being able to set bug B as a duplicate of bug G, and then separately set bug A as another duplicate of G. It would streamline duplicate management if this manual step could be removed. In other words, the duplicate status of "dupes of dupes" could be inherited.

*

Moreover, if such chains of duplicates were managed, AND if the original duplicate relation were kept (and if it were even possible, after going through a warning, to mark a report as a duplicate of a duplicate (due to the reports being virtually identical)), it would allow reports to be grouped based first on identical symptoms and second based on the identified root cause.

Let me illustrate with a diagram:
"->" indicates duplicate relationship, "*X*" indicates a master report.

Practically identical bugs
A -> *B*

Other bugs, different symptoms
C -> *D*

Further duplicate management to master report *G* that discusses the root cause of why A, B and on the other hand C and D are occurring in the first place, and the fixing of which will allow closing bugs A, B, C and D as well:
A -> B \
---------> master report *G*
C -> D /

If a duplicate status is later found wrong (the root cause for bug A and bug B wasn't, after all, bug G), un-duplicating a GROUP of reports at once, WHILE maintaining the duplicate status WITHIN that group (keeping bug A as a duplicate of B), would allow more flexible duplicate management also in a case like this.