Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 378528

Summary: include product and component in task list tool tip
Product: z_Archived Reporter: Sam Davis <sam.davis>
Component: MylynAssignee: Mylyn Inbox <mylyn-inbox>
Status: RESOLVED DUPLICATE QA Contact: Frank Becker <eclipse>
Severity: enhancement    
Priority: P3 CC: shawn.minto
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Sam Davis CLA 2012-05-04 13:35:02 EDT 
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.
Comment 1 Steffen Pingel CLA 2012-05-04 14:12:44 EDT 
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.
Comment 2 Steffen Pingel CLA 2012-05-04 14:14:35 EDT 
Sam, please add your input to bug 197345.

*** This bug has been marked as a duplicate of bug 197345 ***