Hello,

You are probably aware of the problem when people are reporting issues
that lately considered as not a problem or duplicate to already
reported ones. Mostly, this is the result of incorrect test design and
wrong understdnading of software requirements or a product of too many
people working on same area and producing duplicates. Sometimes this is
just a typical human mistake: not following test steps, confusing
correct results with incorrect, etc. I any case I am taking it as a
rewok that could be avoided with right process and due management.

I just wanted to know from professionals who are tracking the amount of
such reports what is the percentage of such reports that they think is
tolerable?

Thanks in advance for the answers.

----
Best WIshes,
Vladimir

In article <1160479279.353849.311230@k70g2000cwa.googlegroups. com>,
"Vladimir Trushkin" <trushkin@tut.by> wrote:

in one of my organisatons, we found that duplicates hovering around the
10% mark were enough of a nuisance to install a filter guy. sadly, they
were not enough of a nuisance to install reasonable testing prior to
integration so we got what we deserverd.

in another organisation, duplicates were so rare that hardly anybody
bothered counting them, and when they occured, those defects were simply
closed with a text reference: duplicate report see ticket 1234567, or
some such. no sweat, no percentages (probably 1-2 %, tops)

how bad is yours?
mats

Matthias Wolpers wrote:

Ours is near 5%... but lately we started to get more duplicates mostly
becuase of more parallelism in test execution. Several people may be
working on same functionality at the same time and, as result, find
same issues.

Having all issues go through one person who filters out duplicates is
our usual practice. But even this does not guarantee duplicates free
defect flow. Finding duplicates is not only responsibility of that
person. He or she also looks at correctness of filling fields in defect
reports, availability of crucial information and correctness of
severity level chosen by reporter.

Sometimes duplicates can be only identified on development side when
root cause of the problem is found out. We ca hardly do anything about
the latter.

----
Best Wishes,
Vladimir