Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332254 - provide a 'compare with' action for tasks
Summary: provide a 'compare with' action for tasks
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 394920 (view as bug list)
Depends on: 198501
Blocks:
  Show dependency tree
 
Reported: 2010-12-09 16:56 EST by David Green CLA
Modified: 2012-11-22 19:17 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Green CLA 2010-12-09 16:56:59 EST 
It would be great to be able to compare tasks with the incoming differences.  Currently when a task has incoming, the task editor shows changed fields with blue highlighting.  It would be great if these changes were also available in a change editor, such that the old values were visible and changes to large values (such as descriptions) were visible with side-by-side comparison.  The UI could be provided by the platform compare editor.
Comment 1 Steffen Pingel CLA 2010-12-09 17:56:03 EST 
+1 As far as I know this existed in the past along with support for the History view to show old "revisions" of a task. 

My sense is that the Task Editor would benefit from an EMF based model which would enable this type of functionality for free.
Comment 2 Miles Parker CLA 2012-11-22 16:22:33 EST 
+1 I like the EMF compare idea (naturally), however I would probably be happy with a simple dialog, e.g.:

Product: SWT -> JFace
Priority P2 -> P3

But a compare dialog would be better for descriptive text.

It's also possible that the change editor is over-weight for this, unless the point is actually to be able to select some values to be reset. But most of my use cases involve just a simple decision -- "do I really want to submit these changes, or are they now obsolete?" Based on that use case, it would be nice to have a "Clear" for outgoing changes esp. if we go with a simpler dialog.
Comment 3 Miles Parker CLA 2012-11-22 16:24:50 EST 
*** Bug 394920 has been marked as a duplicate of this bug. ***
Comment 4 Doug Janzen CLA 2012-11-22 19:17:27 EST 
+1.  It would be great to see _how_ the task has changed.
Comment 5 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST 
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