I'm wondering what should be the best methodology for defect tracking when having more than one product.
I'm using Bugzilla.
Looks like there is no doubt a new product should be created (with its own Versions and Target Milestones). However, we have some modules which are common to both products. Creating new Product means bug duplication..?
It seems to be the correct way but there is a large overhead from duplicating the defects.
I don't use bugzilla, but since you don't post in bugzilla forum, let me add my comment. Before you chose consider the following. Let's call your products A and B and the common module M.
1.1 It is possible that bug in M does not manifest himself in either A or B or even in both of them
1.2 Fixing bug in M that does not manifest in either A or B could still lead to regression in it
2. Your management may want to see report for A in both ways: including M bugs and excluding them
However, we have some modules which are common to both products. Creating new Product means bug duplication..?
<font size="2" face="Verdana, Arial, Helvetica">There is a feature in Bugzilla for cloning bugs that I find very useful.
Lets say there are 2 products productA and productB. And there is a bug that has already been reported for Product A which you have found while currently testing Product B. Then you clone the bug from Product A to Product B. It also creates a dependency to the original bug#(Product A bug in this case). This way, you can track which products the bug needs to be fixed for. Also you can track whether the bug has been fixed for only Product A, only Product B or for both Product A and B.
This cloning feature is available on version 2.20.1 of Bugzilla. So in case you are using a earlier version and if you find the feature missing, then you may want to upgrade to this version.