Control of Multiple Next Actions in Projects
I would like to request the ability to control which next actions show on the home page on a per project basis. GTD dogma suggests that you should review your projects and then add the single next action from that project to your context lists. Others feel this is an inaccurate reading of GTD - you should be able to list multiple next actions. See here: http://www.davidco.com/forum/showthread.php?t=5541&page=1&pp=10
My work day involves a number of single next actions as well as a number of projects, some with many multiple next actions, some with fewer. The projects with many next actions can clutter up my home page making it hard to use effectively. However, I do sometimes need to list multiple next actions from a project on the home page.
Suggestion:
How about setting Tracks up so that the first next action of a project is automatically shown, but also allow additional items to be shown if necessary. Maybe this can be tied into the deferred next actions schema (some sort if indefinitely deferred item, dependent upon the next action above it, or a check box which manually activates it).
Maybe a simpler way to do it is to require next actions that are associated with a project to be added manually by checking a check box. This could be tied into the deferred action schema by making each action an indefinitely deferred action until a check box is checked, when the check box is checked, then it is added to the context lists.
Or maybe this is a refinement of the hidden context schema - next actions associated with projects are hidden until unhidden using a check or some other kind of control.
Or maybe I should just do this manually myself, by associating each project's next actions with a hidden category until I want it unhidden.
My work day involves a number of single next actions as well as a number of projects, some with many multiple next actions, some with fewer. The projects with many next actions can clutter up my home page making it hard to use effectively. However, I do sometimes need to list multiple next actions from a project on the home page.
Suggestion:
How about setting Tracks up so that the first next action of a project is automatically shown, but also allow additional items to be shown if necessary. Maybe this can be tied into the deferred next actions schema (some sort if indefinitely deferred item, dependent upon the next action above it, or a check box which manually activates it).
Maybe a simpler way to do it is to require next actions that are associated with a project to be added manually by checking a check box. This could be tied into the deferred action schema by making each action an indefinitely deferred action until a check box is checked, when the check box is checked, then it is added to the context lists.
Or maybe this is a refinement of the hidden context schema - next actions associated with projects are hidden until unhidden using a check or some other kind of control.
Or maybe I should just do this manually myself, by associating each project's next actions with a hidden category until I want it unhidden.
Leave a comment
+1 for me.
Another suggestion for implementation is to have a "Complete tasks in order" checkbox on the project. If checked, only the first task shows up. Once that one is done and checked off, the next automatically appears in the context list associate with it. If not checked, all tasks show up in their assigned context lists.
Another suggestion for implementation is to have a "Complete tasks in order" checkbox on the project. If checked, only the first task shows up. Once that one is done and checked off, the next automatically appears in the context list associate with it. If not checked, all tasks show up in their assigned context lists.
+1 for me too. I think trandell's suggestion would be helpful. If that could be implemented in addition to subprojects, I think the dependency/multiple-next-action puzzle would be largely solved (assuming the checkbox could exist and differ for projects and their subprojects alike).
I'd really like to see the "Complete tasks in order" feature, but I've got an idea for how to implement it to facilitate even more powerful dependencies. Set up a many-to-many table that allows every task to have any number of dependencies. For "Complete tasks in order," these dependencies would be easy to set up. In the future it may be useful to expose more flexibility and peg more than one dependency to a task.
I started work on this a few months ago but got distracted by some more critical Tracks issues. This branch is wayy behind trunk, but it shouldn't be to hard to merge it up to the present. Is it a useful starting point for you?
"":http://github.com/epall/tracks/tree/dependency_tracking
"":http://github.com/epall/tracks/tree/dependency_tracking