Improperly linked exception report

Someone may want to have a look at because the
JIRA-issue it has been linked to seems to be the wrong one, i.e. the exception
is said to be fixed in 5.1 but it still occurs in #5131 and #5162 with a pretty
different stacktrace. Getting a response to comments posted to JIRA might of
course help as well.

I hope this will not become the standard process that the reporter has to
individually check whether an exception has been linked to the proper JIRA
issue. Automating this process as good as possible is of course important, but
it has to be sufficiently reliable - which seems a bit questionable currently as
I've actually seen this happen several times now.


Please sign in to leave a comment.