| Summary: | provide a 'compare with' action for tasks | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | David Green <greensopinion> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | doug.janzen, milesparker, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 198501 | ||
| Bug Blocks: | |||
|
Description
David Green
+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. +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. *** Bug 394920 has been marked as a duplicate of this bug. *** +1. It would be great to see _how_ the task has changed. 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 |