| Summary: | provide explanation of product abbreviations in task editor and query dialog | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Georg Sendt <georg.sendt> | ||||
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> | ||||
| Status: | CLOSED MOVED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | eclipse, martinae, steffen.pingel | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 2000 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Georg Sendt
Created attachment 75948 [details]
Screenshot
BTW, the description for Aperi you can see on the Bugzilla web interface is "Aperi", so it won't really help much. :-) "Aperi" was just an example. I selected it because I really really don't know what this project is about but you can take any other eclipse project. They all have no description, even no short description, in the bug dialog. If they would have a description I would have a chance to select the right project. Now I only guess or I have to go to eclipse.org and read all the descriptions about the projects to select the right project for the bug. Normally my guess is wrong and someone has to reassign the bug to another project. This takes a lot of time and isn't necessary in my opinion. So please add a description. Georg, I was referring to this page https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=Technology On the other hand, if completely understand your curiosity about the project meaning, but if we'll come from the use case you just described, I am not completely sure if project descriptions would help much. For instance bugs about Ant integration should go into the Ant component of the Platform project, which is descrived as "Eclipse Platform" in Bugzilla. This would be a nice feature. Currently the name of the project is the only thing returned in the configuration rdf. We would have to submit a feature request to Bugzilla requesting that the description be included within the component spec in the rdf. Frank, do you know if this information is available from the repository configuration? If not, we should file a request against Bugzilla. config.cgi?ctype=rdf did not include the description of the product. But if we use the Webservice we have the description. So maybe we should add this an an xmlrpc only feature. Thoughts? Sounds reasonable to me. I have removed the [upstream] tag assuming that the XML-RPC interface already provides the required information. Please let me know if that is not the case and we need to request a Bugzilla enhancement. Steffen, I can no longer find the dialog! Should I store the description in the configuration and use an tooltip for show this if you hover over the control? Or should we close this bug? Thoughts? A tooltip sounds good to me and possibly showing the description in the status bar when scrolling in the combo. 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 |