[
https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-15622:
----------------------------------------
And NetBeans also implemented it in a way that the same exception doesn't open a new
ticket in their Bugzilla, but instead add comments on existing ticket (and probably adds a
vote too). There implementation seems to use a dedicated bugzilla component.
I didn't manage to know if the smartness to find similar report and decide whether to
comment or create a new ticket is on client-side, or if they have a dedicated URL which
decides what to do.
In case of an exception, We might only compare the first stack element of the root
exception. This strategy should be fine enough in a first time. What seems important is to
avoid duplicate reports from the beginning. This would definitely avoid that, and if we
notice too many collisions on a same bug for different issues, we can refine it later.
In term of UI, it's as you said: the Bug Report wizard should pop-up in case of error
with helpful attachement, including the Exception Stack or error message (in case of Error
in log without exception), ask for the users to give a scenario which reproduces test, and
let him select "report". An "hidden" field can make the difference
between an automated report, which would create an entry in an "automated
reports" components, and a human report (someone clicking on "report bug"
menu), which would not set a component. On the jira side, someone have to look at those
issue, and route them to the right component (keeping the "automated report"
tag)
Automatically open/send report when log has error
-------------------------------------------------
Key: JBIDE-15622
URL:
https://issues.jboss.org/browse/JBIDE-15622
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 4.1.1.Alpha1
Reporter: Mickael Istria
JBT should set up an ILogListener on the Eclipse log and send an error report whenever
something is logged as error.
As it's probably not possible to send the error report without asking users, it
should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira