On Oct 30, 2007, at 3:30 AM, Thomas Engelmeier wrote: On 30.10.2007, at 01:09, Chris Espinosa wrote:
I have to disagree here. As far as a developer is concerned, "Duplicate" IS a black hole.
There's no official way to find out.
ADC sends courtesy emails out to originators of duplicate bugs when the original is fixed.
That would imply that all 108 of my reported duplicates are not fixed, which in turn would imply Mail 3.0 is not in an state where I can read this list and send this mail.
There are various reasons you might not get a notice of the disposition of the bug marked "Duplicate":
- It indeed isn't fixed. - It was duped to a dup of the original, and only the first-level dups were notified. - It was duped to a bug that was deferred, but another instance of the bug was fixed without closing out the dups. - It was duped to a bug that was fixed without properly processing the original Radar to note the fix. - It was duped to a bug in Verify/Software Changed that is sitting on one of your fellow developers who hasn't verified it yet - It was filed before DTS started putting the "ADR Duplicate Issue" or "ADC Related Duplicate" tags on bugs.
I haven't gone through all of your 55 active Duplicates, but the ones against my components fall into the above categories (unfixed, dup of a bug still in Verify, dup of a dup).
Some bugs have a notation like the following:
6/14/07 2:17 PM Vanaja Pasumarthi: Now closing. Developer has visibility that this is a duplicate via RadarWeb. Sent courtesy email notifying of duplicate issue. Added Duplicate resolution to ADC Notes. If dev writes in, please provide original issue status or resolution -- whichever is appropriate at the time.
which implies that you do need to "pull" the status of them by writing ADC. If you'd like to do that en masse, you can just give them this:
Those are all your active bugs in Duplicate that you can request the status of.
Chris |