gtg team mailing list archive

[Lionel Dricot <ploum@xxxxxxxxx>]

** Tags added: plugins

-- 
Support concept of projects
https://bugs.launchpad.net/bugs/345513
You received this bug notification because you are a member of Gtg
developers, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
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.