RE: [mylar-dev] confusion between task categories and queries

["Mik Kersten" <beatmik@xxxxxxx>]

Eugene,

We need to keep the UI parts and the infrastructure API parts separate in
discussion of how to improve this support.  The UI needs to be simple and
obvious, and the infrastructure needs to be flexible to support new kinds of
connectors.  Starting with the UI:

* The fact that queries can only show the tasks from one repository, and not
mix local tasks, provides predictability and simplicity.  You always know
that the things that will show up in a query will be the things that match
the query parameters.  

* The user already does not need a query to see changes to tasks that have
been added to a category.  All repository tasks with an offline handler get
synchronized every time if they have changed on the server, no matter where
they are.

* The Archive UI issues that you allude to here are and on bug 162044 are a
problem that we need to address (e.g. duplicate items show when Find pattern
is used), but this are a separate problem with how we expose the archives
and whether we maintain them per-category.

Now regarding infrastructure:

* We already do part of what you suggest: every repository task has a local
task created for it, by virtue of AbstractRepositoryTask being a subclass of
Task.  That's how the repository tasks get the Planning page with scheduling
and notes information.  

* The underlying structure of the Task List is flat--it's just all the
tasks, and the queries layer over top of that.  That's how we can easily
show alternate presentations, e.g. the Archive categories' flat view, the
categories/query view, and the date containers in the Task Activity view.

Let's discuss your suggestions further during the meeting and then follow
up.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Sunday, October 22, 2006 1:24 PM
> To: Mylar developer discussions
> Subject: [mylar-dev] confusion between task categories and queries
> 
> 
>   There is some confusion about task categories and repository queries.
> Right now, when creating task/issue you don't know if it will appear in
> query or not, because query runs at the server side. as a work around,
> task is being added to the root of task list or into the Archive
> category. So, user does not have complete control on the structure of
> the task list and Archive category is getting severely cluttered.
> 
>   I would like to suggest some changes in the architecture of the task
> list that would resolve these issues and will give more flexibility on
> task management and repositories integration.
> 
>   The idea is to always create local tasks. Each task can be
> (optionally) linked to one (or more) repository. In this case, local
> changes will be promoted remotely, as well as remote changes will be
> brought back locally.
> 
>   Then any category could also have one (or more) linked query that
> would bring in new issues created in remote repository. For these query
> hits user could create local tasks, either explicitly, or by scheduling,
> assigning or adding cc'ing self to the task. After that these tasks will
> be showing new updates. Note that user won't need query to see changes
> on monitored tasks.
> 
>   This approach would allow nice mix of local and remote tasks within
> same category.
> 
>   Please comment here and in Bugzilla issue at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=161837#c5
> 
>   regards,
>   Eugene
> 
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev