Exception analyzer problems

There are still problems with the way your exception analyzer works - two days ago I submitted an exception from current version of ReSharper 6.0.2150.5, but this exception was "duplicated" to another already closed issue, resolved, job done... But that's not how it should work - exceptions from newer builds than those, in which issues were "fixed", should not be linked to already closed  tickets and left as resolved. This way you may miss several new regressions, which are mistakenly assigned to similar already closed tickets?
That's my ticket (and it's not the only new ticket assigned to already resolved one I have seen), closed as duplicate, the linked original was closed long time ago:
http://youtrack.jetbrains.net/issue/RSRP-262608

1 comment

Hello Martin,

Exception analyzer checks the value of 'Fixed in build' field of the target
exception and compares it with the version of the exception being processed.
Since  RSRP-134807 has no 'Fixed in build' value, Exception analyzer did
mark the new exception as a duplicate. We will discuss the default behavior
for this case. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

There are still problems with the way your exception analyzer works -
two days ago I submitted an exception from current version of
ReSharper 6.0.2150.5, but this exception was "duplicated" to another
already closed issue, resolved, job done... But that's not how it
should work - exceptions from newer builds than those, in which issues
were "fixed", should not be linked to already closed  tickets and left
as resolved. This way you may miss several new regressions, which are
mistakenly assigned to similar already closed tickets?

That's my ticket, closed as duplicate, the linked original was closed
long time ago:

http://youtrack.jetbrains.net/issue/RSRP-262608

---
Original message URL:
http://devnet.jetbrains.net/message/5302952#5302952



0

Please sign in to leave a comment.