Community
Participate
Working Groups
When I Rclick on an entry in the error log and choose report as bug, a report containing the log entry is generated. ... -- Error Details -- Date: Tue Oct 22 00:38:54 EEST 2013 Message: Keybinding conflicts occurred. They may interfere with normal accelerator operation. Severity: Warning Product: Eclipse 2.0.1.20130919-0803 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.jface Session Data: eclipse.buildId=4.3.0.M20130911-1000 java.version=1.7.0_25 ... The report contains Product and Plugin - those should be autoselected in the report fields in the generated task - they are not autoselected when I right click in this particular snippet above (for instance - this should be present on most kepler installs...) and choose Report as bug > Next > eclipse.org > Finish Thanks
That's an interesting idea. The repository would need provide a mapping from plugins to Bugzilla products and components. Unfortunately I don't see how we could do this without putting custom eclipse.org-specific code into the connector. Perhaps Eclipse itself could provide a mechanism for plugins to declare a Bugzilla product and component, but this seems like more trouble than it's worth.
Also see bug 205196 for a related discussion. *** This bug has been marked as a duplicate of bug 205196 ***
Created attachment 236819 [details] egit : choosing to report to them parses both plugin and project fields Well I happened to submit a bug for egit from the log (Rclick on a warning and selected Report to: Eclipse.org Git team provider (see attached pic) The category was correctly selected : http://www.bild.me/bild.php?file=51439712egit_report.jpg Don't know who's code is this Alternatively on the New task editor couldn't you just parse the text and select the relevant ListView items ? Maybe reopen ?
The o.e.mylyn.bugzilla.ide bundle indeed specifies mapping for some Eclipse projects through the org.eclipse.mylyn.tasks.bugs.support extension point. There is no mapping for the org.eclipse.jface bundle since often errors are caused by other bundles and only caught and logged in JFace. Therefore it's unlikely that we would extend the current list of mappings.
Classifying a bug is the single most difficult step in submitting a bug - trust me, eclipse bugzilla lucks in intuitiveness. Now why not parse the report and set the components to the suggested values ? It will only make things better and less of a chore. After all that is what I did manually - read those values and inputed them - but I guess most users will have to spend some time till they find this trick (I did). I see no reason why you shouldn't do it automatically
