Duplicated State in ClearQuest
I'm in the midst of deploying ClearQuest at my company. Every other defect tracking system that I've used has had Duplicate as a resolution. ClearQuest, by default, has Duplicated as a terminal state. Can anyone think of a good reason to leave defects in the Duplicated state rather than closing them with a resolution of Duplicate? The only advantage that I can see is it makes statistical reporting a tiny bit easier. Our team is all on the fence on the issue. Gut instinct is to close all the dupes, rather than leave them in the Duplicated state as it feels so much cleaner.
Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup