Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 394920 - Provide user details of outgoing changes
Summary: Provide user details of outgoing changes
Status: RESOLVED DUPLICATE of bug 332254
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-22 12:15 EST by Miles Parker CLA
Modified: 2012-11-22 16:24 EST (History)
0 users

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 Miles Parker CLA 2012-11-22 12:15:09 EST 
Sometimes, when a change is not submitted, as user (e.g. Me) will not be able to remember the actual unsubmitted changes made to a task. To help determine whether the changes are still valid it would be helpful to be able to see the changes that would occur if the user submitted the task. Off hand, I can think of two ways of supporting this:

1. Support some kind of diff between current server contents and local task. (Simplest) 
2. Provide user cues for dirty attributes. (Would require some API support as well as significant individual connector UI changes..?)
Comment 1 Steffen Pingel CLA 2012-11-22 15:43:22 EST 
Dirty attributes are marked with a star. Please capture any suggestions that are not already tracked on bug 198501.

*** This bug has been marked as a duplicate of bug 198501 ***
Comment 2 Miles Parker CLA 2012-11-22 16:24:50 EST 
I'm chaging to dup of 332254 as that is really what I wanted here.

Okay, that's an affordance that makes sense, but I don't know how I've missed it all of this time, perhaps my eyesight needs checked or a color change would be helpful.

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