Bugzilla – Full Text Bug Listing
| Summary: | Include EPP packaging names in bug reports | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Kevin McGuire <Kevin_McGuire> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | bokowski, mknauer, robert.elves, steffen.pingel, the.ubik |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Kevin McGuire
Suggestion is to use the whiteboard for the packaging. I was about to propose some UI for this and then realized that having the user choose the EPP packaging that they download is somewhat un-Mylyn because it can be automated. What if we instead had EPP create a plug-in or configuration directory that listed the ID and name for the Eclipse packaging, and just had Mylyn use that? Markus: to do this properly we need the EPP packagings to provide an identifier that we can retrieve at runtime. Sometimes I wonder if they should have a different Product ID, because they really are somewhat different than the bare SDK (-product org.eclipse.sdk.ide) but that may be a bit much. Thoughts? (In reply to comment #3) > Markus: to do this properly we need the EPP packagings to provide an identifier > that we can retrieve at runtime. Sometimes I wonder if they should have a > different Product ID, because they really are somewhat different than the bare > SDK (-product org.eclipse.sdk.ide) but that may be a bit much. Thoughts? A different product ID seems reasonable to me. They *are* acting like products, just nobody is calling them that. But in the future one could imagine custom welcome screens, customized look... that is, they could easily be more than just a collection of plugins. Due to time constraints I wasn't able to finalize the mapping API for repositories and products. Deferring to the next milestone. Starting with Galileo EPP packages will have distinct product ids which are now automatically added to the description if a bug is reported from the error log. This will work if the user creates a bug report from an error log entry or uses Help > Report Bug but not for the general case when bugs are created from the Task List. I do like the idea of using the status whiteboard for providing additional configuration details but we currently do not have a good extension mechanism for that in the Bugzilla connector. We could also consider adding a checkbox for attaching configuration details or a button to populate the status whiteboard but that would require additional discussion and some customization. I am not sure this is useful for all bug repositories particularly if non-Eclipse products are tracked. I think the report from error log enhancements cover an important part of this request. I'll put this on the backlog for now and we can consider further improvements for a future release. *** Bug 420108 has been marked as a duplicate of this bug. *** 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 |