Exception submission change

In the new build it seems like sometimes I manage to submit an exception
and sometimes it fails.

Qs:

1. Why the option to open the submitted / existing tracker item got removed?

2. Why does it fail sometimes (consistently, I always try more than
once) but when it succeeds it's always on the 1st time? Does it succeed
only on non-submitted exceptions?

Lastly, the comments entered are not preserved if submission fails - the
submission dialog comes back empty after the error message.

Thanks,
Amnon

9 comments
Comment actions Permalink

Hello Amnon,

AG> 1. Why the option to open the submitted / existing tracker item got
AG> removed?

Some of the exception reports contain private data (fragments of source code),
so making all submitted exceptions publically available caused leaks of sensitive
information.

It may be possible to implement a scheme allowing the user to view only the
ITN requests submitted by himself, but I don't quite see what benefit would
it bring.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Not being able to view the submitted ITN request is not a big deal.

However, if it is not available then please don't present the user with the option of viewing it, only to fail if attempted.

Having a user-unfriendly interface doesn't make eap users like me eager to continue using the exception report mechanism.

0
Comment actions Permalink

Hello Tim,

TH> Not being able to view the submitted ITN request is not a big deal.
TH>
TH> However, if it is not available then please don't present the user
TH> with the option of viewing it, only to fail if attempted.

The option has already been removed.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Amnon I. Govrin wrote:

In the new build it seems like sometimes I manage to submit an exception
and sometimes it fails.

Qs:

1. Why the option to open the submitted / existing tracker item got
removed?


I see that Dmitry answered this one (IIRC there was a JIRA item about it
recently)...

2. Why does it fail sometimes (consistently, I always try more than
once) but when it succeeds it's always on the 1st time? Does it succeed
only on non-submitted exceptions?


...but not this one. I came to the same conclusion as you. It would be
nice if it came back and said "Already submitted, thanks" or similar.

Lastly, the comments entered are not preserved if submission fails - the
submission dialog comes back empty after the error message.


That's why you have an always-open editor to receive the copied'n'pasted
message before submitting the first time (not that it annoys me too, of
course...).

--
Mark Scott
mark@codebrewer.com

0
Comment actions Permalink

Same here -- submitting errors has been very flaky, of late.

0
Comment actions Permalink

Ditto.

In the last build it's been so flaky I've stopped submitting bugs, since it more often fails than not.

0
Comment actions Permalink

Hello Amnon,

AG> 2. Why does it fail sometimes (consistently, I always try more than
AG> once) but when it succeeds it's always on the 1st time? Does it
AG> succeed only on non-submitted exceptions?

First, the assumption that there is some sort of duplicate detector that
causes submission to fail if the exception is a duplicate is wrong. All duplicate
detection is performed by the Exception Analyzer after the exception has
been submitted to ITN.

Second, the exception submission is a multi-step process: first, a new ITN
request is created, and then comments are optionally added providing additional
details for the exception. As far as I understand, what happens now is: the
initial report is usually created successfully, but the posting of comments
no longer works because of the ITN security changes or the recent JIVE forums
upgrade. So the exceptions do get into ITN, but you get a "failure" report
because an optional submission step fails.

To summarize: don't believe the "failed" report, and we'll try to clear things
up on our side.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Thanks for the update.

0
Comment actions Permalink

It may be possible to implement a scheme allowing the user to view
only the ITN requests submitted by himself, but I don't quite see what
benefit would it bring.


For one thing, I could add more information as I encounter the bug again,
and perhaps figure out how to reliably reproduce it.

That said, I don't realy care about that much, but I did like being to open
my exceptions because then I could see (or get notified) when they got closed.
If I could get an email when one of my exceptions was fixed, that would
be good enough for me. It would make me feel like what I'm doing is useful.
Right now, I just feel like none of my problems have been fixed.

Tobin


0

Please sign in to leave a comment.