Allow Defect Reuse - "Repeat" Defects
Sometimes, in a chunk of code, the developer repeats the same mistake in several distinct places. For example, they forget to put a header at the start of a function in several places, or they use inline strings when your coding standards are to use a home brewed string resource. It'd be nice to say 'This defect on this line is another instance of defect XXXXX" instead of repeating what was written already. This would be an "Associated" defect, or "Repeated" defect. Each defect is distinct, but each has the same root cause / bad design / problem / algorithmic issue.
You would want the text from the original to show up, as well as a way to edit it. Those edits would be reflected on all of the associated defects. You'd probably also want a way to de-associate it, but maybe not.
pepkaro
shared this idea
4 comments
-
dkarr
commented
I often have a similar problem. I usually cut/paste the text of the original comment in several other files. An indication that this comment/defect is the same as another one would be useful.
-
Srikanth
commented
Instead of the term "Defect Reuse", I think this is more like "Same defect as xyz". Currently there are two ways to do this. 1. Add multiple defects or 2. Add one defect and Add comment in all other places referring "Same as defect xyz". Going with mutiple defect works great when we want to track closure for each and every instance identified, but when it comes to metrics, it shows up badly. If I do a mistake without knowing that I am making a mistake, then I should be given an opportunity to correct it and not be looked like a criminal by my management who reviews the count of defects that I make. Adding a comment looses tracking capability and it allows closing the review without fixing all instances. So I vote 2 count on this since it allows us to count the right number of defects instead of wrongly counting which skews metrics.
-
Michael Miller
commented
I agree, this would be a very nice feature so the reviewer does not have to retype each instance a particular bug occurred and where the coder could group them under a single defect. Then, when he corrects the defect, all the items are handled in a single click.
-
Garen
commented
