Quote:
|
Originally Posted by brooce
If they're ALL next actions, then NONE of them are next actions.
|
True, but beside the point.
The issue is, SOME projects have actions that can truly be carried out in parallel. Think of cooking a meal of stir-fried beef and peppers. We can do the prep work for the stir-fry in any order -- it doesn't matter whether we cut the red pepper first or the green, or whether we do the garlic before the ginger. So, under the "knife work" sub project,
any task can be the next step, and we might do them in different orders on different days.
However, in the "cook" sub-project, we do have to follow a series of steps in exact order. If we try to cook the peppers first, they will overcook in the time it takes to cook the beef.
Now, if we were to enter this in OF, we'd have, in Project View:
Project: Cook Pepper Beef
Sub-P: Prep Work
Task: cut red pepper Context: Knife
Task: cut green pepper Context: Knife
Task: cut beef Context: Knife
....
Sub-P: Stir-Fry
Task: Cook beef Context: Wok
Task: Cook peppers Context: Wok
Task: add ginger & garlic Context: Wok
....
In Context View, the one we'll see during cooking:
Context: Knife
Task: cut red pepper
Task: cut green pepper
Task: cut beef
...
Context: Wok
Task: Cook beef
Task: Cook peppers
Task: add ginger & garlic
....
Note the purple Next Actions.
If we set the filter to Show next actions, we can't see all the knife tasks, though we want to. But if we set Available Actions, we'd see the Knife tasks for several other meals as well. What we want (well, what I want) is to set ALL the knife work tasks in this project to Next Actions, so I could see them all at once.
[No, I don't plan out my cooking — but this is an example most people can understand.]
--Liz