Community
Participate
Working Groups
Actually error log entries can be used as a source for new bug reports. The problem is that log entries with stack traces can be very long, and make the description look very noisy. Maybe it is better to create the report with the log entry as a attachment? One issue is that actually Mylyn does not allow to create a attachment during bug creation. Following is Eugene's comment that suggested this idea initially: -- Created from Comment -- URL: https://bugs.eclipse.org/bugs/show_bug.cgi?id=215071 Comment: 5 Is all logs put into the description text? I am bit concerned that it would make it too long and in result less readable. Maybe such large logs should be posted as attachments, and then provide a convenience feature to open log in the Error Log view, which allows to import logs for browsing (though I am not sure if these actions are public api).
Note that until we get attachment search, this would mean that search and duplicate detection would not work on the corresponding bug reports. Those are important features, so even though this approach makes sense I think that it would need to be optional, and potentially discouraged by the UI until we get them. Please consider voting on the corresponding Mozilla bug. 142188: Attachment search. https://bugzilla.mozilla.org/show_bug.cgi?id=142188
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
