Tracking Defects in Multiple Code Streams
We have a need to track the same defect in 3 or more parallel code streams (e.g.when we find and fix a defect, it must be addressed in a service pack for the past 2 releases, well as the release under development.) Currently we "clone" the defect and end up with 3 loosely linked defects. We need different workflows for each defect. Keeping track of what has been fixed and tested is a bit of a nightmare when you're dealing with high volumes.
Has anyone found a defect tracking tool that does a good job of this?
Has anyone defined a process that makes this easier?
How do you reflect this situation in metrics? As 1 defect or 3?
Re: Tracking Defects in Multiple Code Streams
On the metrics question: depends what you're using the measure for.
If you're doing root cause analysis there's one defect.
If you're preparing a customer advice such as an FAQ there's one defect for someone to write up.
If you're estimating how much time it will take to fix and re-test there are three defects.
When tracking actual progress there are three defects because you have to test and sign off on each stream separately.