Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

When a bug has 40 votes, and then (or anytime) gets marked as a duplicate of another bug, the votes of the old (dup) one are "lost".
Scenario: a grave bug gets submitted many times by many users as duplicates, and randomly others find them before gathered together under one, and vote for them - so all really have the same goal.


This should not be.

Reproducible: Always

Steps to Reproduce:
look at bug #289711, at #289863 and at #281955 - one is a dupe of the other, but the main bug has only 20 votes (ATM). This is just an example.

Actual Results:  
When the bug now is marked as dupe, all the votes of this bug stay where they are, but the new main bug maybe has 0 votes.

Expected Results:  
whenever bug A is marked as a dupe of bug B, the votes should be gathered together in the main bug.
this could be done like:
when counting (and showind) the votes of a bug, count the votes of this bug, then look recursively at all the duplicates, and count their votes as well (as long their votes are not of the same user, so avoid double counting).

I think Ubuntu Brainstorm does this in some way.