Community
Participate
Working Groups
Task list tooltip should show info about project and component. Right now it is hard to see what component/project task belong to without opening editor (especially important for all tasks dumped into Archive). Generally these attributes are connector specific (i.e. trac have just one project), but it still may worth to add project and component attributes to the AbstractTask class (would be much easier to deal with them if AbstractTask allowed arbitrary attributes). An alternative option is to add toString() implementation for all subclasses of the AbstractTask and use that method when creating tooltip layout.
Steffen: you're not the tooltip guy :)
It is okay to load task data when displaying the tooltip so the exising mapping for "Product" could be used to display the component/project. Adding a toString() method will not help much as task data should not be coupled to AbstractTask. A method could be added to AbstractRepositoryConnectorUi for providing connector specific tooltip content or an extension point could be defined.
I think standardizing on attributes would make it easier to integrators and will require less coding comparing new api and extension points.
We also show product and component in the header of the attribute section in the task editor. I like the idea to show the in the tooltip as well. I wouldn't want to keep that information in the data model as that would get very expensive memory wise. We should compute that dynamically, e.g. by invoking new API on AbstractRepositoryConnectorUi. Personally, I would also like to see the milestone which we use to indicate whether a bug is scheduled for a release or has been resolved for a release.
*** Bug 378528 has been marked as a duplicate of this bug. ***
From duplicate: > The product and component are often essential to defining what a Bugzilla task > is, so they should be included in the TaskListToolTip. They are far more > important to me than the estimate. We have been including this information in > the summary of some bugs partly as a workaround but that kind of duplication is > not good. > > Since some other connectors have fields which roughly correspond to product and > component, we could consider adding framework support for identifying these > fields somehow, so that they are included in the same line of the tooltip for > all such connectors. The number of these fields could be different than 2 > though. Perhaps the connector would need to return a formatted string. This > could of course be accomplished using > ITasksCoreConstants.ATTRIBUTE_TASK_EXTENDED_TOOLTIP but that might not give it > enough prominence.
(In reply to comment #4)> > Personally, I would also like to see the milestone which we use to indicate > whether a bug is scheduled for a release or has been resolved for a release. This makes me wonder if the tooltip should be customizable, as the relevance of different fields could vary widely from one project to another. Could be a private setting, or could be stored on the repository (could even be different for different products).
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
