Hello!
I was trying Mylyn 2.0 in Eclipse 3.3 (before I just used Mylar 1.0 in
Eclipse 3.2 for a while) and I was wondering how Bugzilla tasks are
handled...
I mean: when a task is moved to the archive category?
In Mylar 1.0, when a bug was set to RESOLVED/VERIFIED/CLOSED state, the
corresponding task was moved to the archive category...
But now, with Mylyn 2.0, I just added a query in my task view and I
cannot understand why:
- the tasks associated with some CLOSED bugs are in the archive
category, some are not
- the tasks associated with some NOT closed bugs (one is ASSIGNED, one
is NEW, for example) are in the archive category (!!!)

Moreover, I cannot find a way to manually move a bug from or to the
archive category (there is no move to => archive category menu item,
while drag 'n' drop does not do the job)...

Mauro Molinari ha scritto:
> - the tasks associated with some CLOSED bugs are in the archive
> category, some are not
> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
> is NEW, for example) are in the archive category (!!!)

I think I was not very clear...
I meant:
- some tasks associated with CLOSED bugs are in the archive category,
some are not
- some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
NEW, for example) are in the archive category, while I expected all such
tasks not to be there

Mauro Molinari wrote:
> Mauro Molinari ha scritto:
>> - the tasks associated with some CLOSED bugs are in the archive
>> category, some are not
>> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
>> is NEW, for example) are in the archive category (!!!)
>
> I think I was not very clear...
> I meant:
> - some tasks associated with CLOSED bugs are in the archive category,
> some are not
> - some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
> NEW, for example) are in the archive category, while I expected all such
> tasks not to be there
>
> Mauro.

IHMO, there are usability issues with the "archive category" concept
like you pointed out that make it hard to understand.

Please do voice any complaints that you have on the bug that Willian has
pointed out.

For the time being note that the policy is simple and not specific to
any connector. When the Task List is focused all repository tasks show
in the archive category. When not focused only the tasks that need to
show (i.e. no longer match any query but have incomings or are overdue)
will show in the archive.

To avoid having tasks unnecessarily fall into the archive we recommend
setting up your queries to match both opened and closed bugs:

Mauro Molinari wrote:
> Mauro Molinari ha scritto:
>> - the tasks associated with some CLOSED bugs are in the archive
>> category, some are not
>> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
>> is NEW, for example) are in the archive category (!!!)
>
> I think I was not very clear...
> I meant:
> - some tasks associated with CLOSED bugs are in the archive category,
> some are not
> - some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
> NEW, for example) are in the archive category, while I expected all such
> tasks not to be there
>
> Mauro.

Mik Kersten ha scritto:
> Mauro,
>
> Please do voice any complaints that you have on the bug that Willian has
> pointed out.
>
> For the time being note that the policy is simple and not specific to
> any connector. When the Task List is focused all repository tasks show
> in the archive category. When not focused only the tasks that need to
> show (i.e. no longer match any query but have incomings or are overdue)
> will show in the archive.
>
> To avoid having tasks unnecessarily fall into the archive we recommend
> setting up your queries to match both opened and closed bugs:
>
> http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Query_set up
>
> Mik

Dear Willian and Mik,
thanks for your help.
Before filing a new bug report or update an existing one, I would like
to understand if I am doing/understanding something wrong or if these
are real Mylyn problems.

You say that the archive category is needed to host tasks which are not
in any other category. Mik also suggests to make queries containing both
open and closed bugs to avoid some bugs to unnecessarily fall into the
archive...
Although, from this point of view, I would prefer to make a query
showing just the open bugs, so that when I close one, it goes to the
archive category automatically...

Anyway, as soon as we say that the archive category behaviour is the one
you mentioned, I cannot understand what I'm going to explain.

First of all, I deleted all my tasks and queries, to start over from
scratch.
(by the way: you can delete single tasks from the archive category, but
you cannot delete single tasks from a category mapped to a query... it
might sound obvious, but I think it's a bit confusing for the user)

Then, I created a new query, containing all bugs assigned to me, coming
from our local bugzilla repository. After doing that, the new category
appeared in the task list, with many new tasks under it... BUT... also
new tasks automatically appeared in the archive category!!

If I delete all my tasks again and re-create the same query, then some
different tasks seem to appear in the archive category.
I then tried to close and reopen Eclipse and now the archive category
shows all the tasks in my query category... but hadn't we said that it
should contain just not-categorized tasks?

So, it seems that the archive category has some strange
not-deterministic behaviours... and/or it seems not to properly update
as soon as you do some changes to the task list (for instance, you
create a new query)...

I also would like to know your opinion about other issues like:

- you cannot rename a category mapped to a query (right click -> rename
-> type new name -> Enter --> does nothing!)

- (as said before) you cannot delete a task from a category mapped to a
query and you cannot move tasks from/to it

- every time you close and reopen Eclipse, the "Filter Archive Category"
in task view is reset

- I would personally better need a special category named "completed
tasks" where all completed task fall as soon as I mark them as completed
(i.e.: I fix/close a bug); filtering out the completed tasks is not what
I would really need, because I may have to pick those tasks up again for
a while

Mauro Molinari wrote:
....
> You say that the archive category is needed to host tasks which are not
> in any other category. Mik also suggests to make queries containing both
> open and closed bugs to avoid some bugs to unnecessarily fall into the
> archive...
> Although, from this point of view, I would prefer to make a query
> showing just the open bugs, so that when I close one, it goes to the
> archive category automatically...

The UI is designed around filtering completed completed tasks and
allowing you to quickly search for ones that are filtered. It's
generally better to rely on categories for this because the query is
currently the best way of specifying and grouping the set of tasks that
you are interested in (e.g. all for a specific milestone, assigned to a
specific person, etc.)

> Then, I created a new query, containing all bugs assigned to me, coming
> from our local bugzilla repository. After doing that, the new category
> appeared in the task list, with many new tasks under it... BUT... also
> new tasks automatically appeared in the archive category!!
>
> If I delete all my tasks again and re-create the same query, then some
> different tasks seem to appear in the archive category.
> I then tried to close and reopen Eclipse and now the archive category
> shows all the tasks in my query category... but hadn't we said that it
> should contain just not-categorized tasks?

The archive contains all repository tasks. Make sure that you either
have Filter Archive Category selected in the view menu or that you click
"Focus on Workweek".

> So, it seems that the archive category has some strange
> not-deterministic behaviours... and/or it seems not to properly update
> as soon as you do some changes to the task list (for instance, you
> create a new query)...

Any non-deterministic behavior would be a serious bug, so if you can
reproduce that please report.

> I also would like to know your opinion about other issues like:
>
> - you cannot rename a category mapped to a query (right click -> rename
> -> type new name -> Enter --> does nothing!)

Not sure what you mean by "category mapped to a query". But I just
checked and this is indeed a bug so please report it. For now the work
around is to open the query to change its name.

> - (as said before) you cannot delete a task from a category mapped to a
> query and you cannot move tasks from/to it

You are either noticing the slightly weird interaction we have between
repository tasks and the Uncategorized category, or you should be using
Remove from Category instead of delete. Either way, please file a bug
so we can figure out if there is a problem or how better to meet
expectations here.

> - every time you close and reopen Eclipse, the "Filter Archive Category"
> in task view is reset

Yes, this is not intended to be an option that persists because of all
the problems that having the archive visible causes. However, Eclipse
conventions dictate that all settings of this sort should be persisted,
so we have to change something there. If you have use cases for it
being visible please comment on:

> - I would personally better need a special category named "completed
> tasks" where all completed task fall as soon as I mark them as completed
> (i.e.: I fix/close a bug); filtering out the completed tasks is not what
> I would really need, because I may have to pick those tasks up again for
> a while

This would only meet the use case of tasks 'falling' out of queries that
are set on resolution/completed status. But the archive also needs to
show tasks that you worked on that no longer match a query based on
another attribute, such as a component or milestone. This is one of the
reasons why we made completion be a first class and fixed part of the
UI, whereas we made queries and their attributes be a configurable and
connector-specific part of the UI.

Mauro Molinari ha scritto:
> - the tasks associated with some CLOSED bugs are in the archive
> category, some are not
> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
> is NEW, for example) are in the archive category (!!!)

I think I was not very clear...
I meant:
- some tasks associated with CLOSED bugs are in the archive category,
some are not
- some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
NEW, for example) are in the archive category, while I expected all such
tasks not to be there

Mauro Molinari wrote:
> Mauro Molinari ha scritto:
>> - the tasks associated with some CLOSED bugs are in the archive
>> category, some are not
>> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
>> is NEW, for example) are in the archive category (!!!)
>
> I think I was not very clear...
> I meant:
> - some tasks associated with CLOSED bugs are in the archive category,
> some are not
> - some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
> NEW, for example) are in the archive category, while I expected all such
> tasks not to be there
>
> Mauro.

IHMO, there are usability issues with the "archive category" concept
like you pointed out that make it hard to understand.

Please do voice any complaints that you have on the bug that Willian has
pointed out.

For the time being note that the policy is simple and not specific to
any connector. When the Task List is focused all repository tasks show
in the archive category. When not focused only the tasks that need to
show (i.e. no longer match any query but have incomings or are overdue)
will show in the archive.

To avoid having tasks unnecessarily fall into the archive we recommend
setting up your queries to match both opened and closed bugs:

Mauro Molinari wrote:
> Mauro Molinari ha scritto:
>> - the tasks associated with some CLOSED bugs are in the archive
>> category, some are not
>> - the tasks associated with some NOT closed bugs (one is ASSIGNED, one
>> is NEW, for example) are in the archive category (!!!)
>
> I think I was not very clear...
> I meant:
> - some tasks associated with CLOSED bugs are in the archive category,
> some are not
> - some tasks associated with not CLOSED bugs (one is ASSIGNED, one is
> NEW, for example) are in the archive category, while I expected all such
> tasks not to be there
>
> Mauro.

Mik Kersten ha scritto:
> Mauro,
>
> Please do voice any complaints that you have on the bug that Willian has
> pointed out.
>
> For the time being note that the policy is simple and not specific to
> any connector. When the Task List is focused all repository tasks show
> in the archive category. When not focused only the tasks that need to
> show (i.e. no longer match any query but have incomings or are overdue)
> will show in the archive.
>
> To avoid having tasks unnecessarily fall into the archive we recommend
> setting up your queries to match both opened and closed bugs:
>
> http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Query_set up
>
> Mik

Dear Willian and Mik,
thanks for your help.
Before filing a new bug report or update an existing one, I would like
to understand if I am doing/understanding something wrong or if these
are real Mylyn problems.

You say that the archive category is needed to host tasks which are not
in any other category. Mik also suggests to make queries containing both
open and closed bugs to avoid some bugs to unnecessarily fall into the
archive...
Although, from this point of view, I would prefer to make a query
showing just the open bugs, so that when I close one, it goes to the
archive category automatically...

Anyway, as soon as we say that the archive category behaviour is the one
you mentioned, I cannot understand what I'm going to explain.

First of all, I deleted all my tasks and queries, to start over from
scratch.
(by the way: you can delete single tasks from the archive category, but
you cannot delete single tasks from a category mapped to a query... it
might sound obvious, but I think it's a bit confusing for the user)

Then, I created a new query, containing all bugs assigned to me, coming
from our local bugzilla repository. After doing that, the new category
appeared in the task list, with many new tasks under it... BUT... also
new tasks automatically appeared in the archive category!!

If I delete all my tasks again and re-create the same query, then some
different tasks seem to appear in the archive category.
I then tried to close and reopen Eclipse and now the archive category
shows all the tasks in my query category... but hadn't we said that it
should contain just not-categorized tasks?

So, it seems that the archive category has some strange
not-deterministic behaviours... and/or it seems not to properly update
as soon as you do some changes to the task list (for instance, you
create a new query)...

I also would like to know your opinion about other issues like:

- you cannot rename a category mapped to a query (right click -> rename
-> type new name -> Enter --> does nothing!)

- (as said before) you cannot delete a task from a category mapped to a
query and you cannot move tasks from/to it

- every time you close and reopen Eclipse, the "Filter Archive Category"
in task view is reset

- I would personally better need a special category named "completed
tasks" where all completed task fall as soon as I mark them as completed
(i.e.: I fix/close a bug); filtering out the completed tasks is not what
I would really need, because I may have to pick those tasks up again for
a while

Mauro Molinari wrote:
....
> You say that the archive category is needed to host tasks which are not
> in any other category. Mik also suggests to make queries containing both
> open and closed bugs to avoid some bugs to unnecessarily fall into the
> archive...
> Although, from this point of view, I would prefer to make a query
> showing just the open bugs, so that when I close one, it goes to the
> archive category automatically...

The UI is designed around filtering completed completed tasks and
allowing you to quickly search for ones that are filtered. It's
generally better to rely on categories for this because the query is
currently the best way of specifying and grouping the set of tasks that
you are interested in (e.g. all for a specific milestone, assigned to a
specific person, etc.)

> Then, I created a new query, containing all bugs assigned to me, coming
> from our local bugzilla repository. After doing that, the new category
> appeared in the task list, with many new tasks under it... BUT... also
> new tasks automatically appeared in the archive category!!
>
> If I delete all my tasks again and re-create the same query, then some
> different tasks seem to appear in the archive category.
> I then tried to close and reopen Eclipse and now the archive category
> shows all the tasks in my query category... but hadn't we said that it
> should contain just not-categorized tasks?

The archive contains all repository tasks. Make sure that you either
have Filter Archive Category selected in the view menu or that you click
"Focus on Workweek".

> So, it seems that the archive category has some strange
> not-deterministic behaviours... and/or it seems not to properly update
> as soon as you do some changes to the task list (for instance, you
> create a new query)...

Any non-deterministic behavior would be a serious bug, so if you can
reproduce that please report.

> I also would like to know your opinion about other issues like:
>
> - you cannot rename a category mapped to a query (right click -> rename
> -> type new name -> Enter --> does nothing!)

Not sure what you mean by "category mapped to a query". But I just
checked and this is indeed a bug so please report it. For now the work
around is to open the query to change its name.

> - (as said before) you cannot delete a task from a category mapped to a
> query and you cannot move tasks from/to it

You are either noticing the slightly weird interaction we have between
repository tasks and the Uncategorized category, or you should be using
Remove from Category instead of delete. Either way, please file a bug
so we can figure out if there is a problem or how better to meet
expectations here.

> - every time you close and reopen Eclipse, the "Filter Archive Category"
> in task view is reset

Yes, this is not intended to be an option that persists because of all
the problems that having the archive visible causes. However, Eclipse
conventions dictate that all settings of this sort should be persisted,
so we have to change something there. If you have use cases for it
being visible please comment on:

> - I would personally better need a special category named "completed
> tasks" where all completed task fall as soon as I mark them as completed
> (i.e.: I fix/close a bug); filtering out the completed tasks is not what
> I would really need, because I may have to pick those tasks up again for
> a while

This would only meet the use case of tasks 'falling' out of queries that
are set on resolution/completed status. But the archive also needs to
show tasks that you worked on that no longer match a query based on
another attribute, such as a component or milestone. This is one of the
reasons why we made completion be a first class and fixed part of the
UI, whereas we made queries and their attributes be a configurable and
connector-specific part of the UI.