Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337768 - Normalize interest values when merging contexts
Summary: Normalize interest values when merging contexts
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:
Depends on:
Blocks:
 
Reported: 2011-02-21 15:57 EST by Sam Davis CLA
Modified: 2011-02-21 16:04 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 Sam Davis CLA 2011-02-21 15:57:13 EST 
It would be better to normalize interest values when merging contexts.

See 331172: warn when copying context to a task that already has context
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331172

From comment #9:
> after you
> merge 2 contexts, the elements in the merged context that are interesting might
> all come from only one of the original contexts. We could try to change the date
> stamps on events or somehow normalize interest levels between the 2 contexts,
> because the user might expect/want the set of interesting elements in the merged
> context to be roughly the union of the interesting elements in the 2 original
> contexts. Otherwise, the difference between merge and Add might not be
> noticable in some cases.
Comment 1 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