gtg team mailing list archive

[Bryce Harrington <345513@xxxxxxxxxxxxxxxxxx>]

** Summary changed:

- Inactive tasks should not be displayed in the main list
+ [Needs plugin] Inactive (project) tasks should not be displayed in the main list

-- 
[Needs plugin] Inactive (project) tasks should not be displayed in the main list
https://bugs.launchpad.net/bugs/345513
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
Currently tasks can have one of two statuses:  "Active" and "Done".  Please add support for a third state called "Inactive", with the following traits:

Inactive tasks...
 * don't show up in the All Tasks listing
 * don't show up in the work view
 * don't show up in the 'Closed tasks' listing
 * show up in the tag listing only if they have that tag (they don't show and aren't counted in parent tags unless they also have the parent's tag)
 * are displayed in gray text rather than black

When you enter new subtasks under an 'Inactive' parent task, those new subtasks are given status 'Inactive'.
When you mark an 'Inactive' or 'Done' parent task to 'Active', all of its subtasks in state 'Inactive' are set to 'Active'.
When you mark an 'Active' parent task to status 'Inactive' or 'Done', all of its subtasks in state 'Active' are set to 'Inactive'.


[Original Report]
A "super task" (a task with sub-tasks) can be used to represent a project but it would be nice if we could explicitly convert such tasks into projects. It would lead to some different behavior.

For example a project without any sub-task would not appear in the work view because it's a project and it is thus not directly actionable. Also an active project without any active sub-task would be colored in red because some sub-tasks must be planified in order to ensure that progress is made. Also some properties change on the project would auto-apply to all sub-tasks. Marking a project as inactive must mark all sub-tasks as inactive. Reactivating one of the sub-task would move the project out of its inactive state.

Note that I spoke twice of active/inactive projects/tasks and I really believe that you should support this concept because it is central to the way I organize my work. When I start a new project, I describe all the tasks that must be done inside the project but they are all inactive. Then every week when I plan my work, I move some of the tasks into an active state (either to do "ASAP" or at some specified date in the future) and in my work view, I only want to see the active tasks and not all the other sub-tasks that have not yet been activated.