Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 181386 - Don't notify changes on "Archive" category
Summary: Don't notify changes on "Archive" category
Status: RESOLVED DUPLICATE of bug 165809
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 2.0 M2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-06 04:42 EDT by Willian Mitsuda CLA
Modified: 2007-04-11 18:07 EDT (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 Willian Mitsuda CLA 2007-04-06 04:42:52 EDT 
My use case:

- At my work I had my internal corporate bugzilla installation and Eclipse.org bugzilla repositories configured on Mylar.
- I had a bunch of queries on both repositories.
- I was getting a bunch of notifications from Eclipse.org, then I deleted the queries, so I could work ;)
- The problem is that Mylar still synchronizes tasks who are not visible on task list (and consequently fall on "Archive" category) and they keep polluting my task list.

IMHO, task list should synchronize (or at most notify on UI) only tasks visible on current task list model point of view (I'm considering that with the current merge of task planning it can have other models in future).
Comment 1 Mik Kersten CLA 2007-04-10 01:28:53 EDT 
Our current design is that everything in the Task List gets synchronized, in order to keep the mental model simple and to ensure that users don't accidentally fail to get notified of changes on a task if their query stops matching it.  However, this is not an uncommon use case and one of the Mylar 2.0 Plan items is dedicated to addressing it.  Please comment on bug 165809 if there is anything additional that needs to be done to support your use casel

*** This bug has been marked as a duplicate of bug 165809 ***
Comment 2 Willian Mitsuda CLA 2007-04-10 15:05:57 EDT 
Hum... I don't see how this can be a duplicate of bug#165809. Is this the right bug?
Comment 3 Mik Kersten CLA 2007-04-10 20:36:49 EDT 
The idea is that we will support suppressing synchronization on a per-repository basis.  So whether the tasks are in the Archive/Uncategorized bin or not, you will not be notified of changes if you have put that repository offline (e.g. because of moving jobs).
Comment 4 Willian Mitsuda CLA 2007-04-11 11:06:03 EDT 
OK, it seems reasonable for my case.
Comment 5 Mik Kersten CLA 2007-04-11 18:07:07 EDT 
Great.  That will keep the UI simple.