This topic is for comments on the original blog entry at: http://blog.gtdnext.com/beta-2-released/
Great comment in the blog about checklists (info). A very useful feature, too 
But I must say, honestly, that I did not at all understand the description about “Force Next at the Project Level”. It does not seem to describe what you tentatively described ( http://forum.gtdnext.com/t/some-thoughts-on-gtdnext-next-action-logic ) nor what anyone has ever asked for (as far as I understand it). The way I read the blog post was that if you make a gray project green then all new actions in that project will default to parallel from then on. What would be the the point of that? And how does this tally with the fundamental necessity to be able turn entire projects or subprojects “off”? It would seem more natural and consistent to me that green means “on” (allowing green sub-items to be visible on the active/main lists) and gray means “off” (hiding all sub-items, regardless of color and level, from the active/main lists), as discussed earlier.
The problem we are solving with “Force Next at Problem Level” is the report from users where they felt they might forget a new task added to a project already in flight. There are a number of ways to solve this problem. One of the ways we solved this problem is with a change to our drag and drop feature, so that all actions dragged onto a project in the left pane now appear at the top of the project as next actions. Another way we are addressing the problem is with this feature. Now, users can turn on this feature to make any new actions in the project appear on their next action list via the force next function.
This feature does not address the issue of allowing projects to be sequential or parallel. That is a different issue and we are still working on exactly how we will address that. Apologies if it sounded like this feature would address that problem. In my mind they are two different problems that need addressing.
Yes, I think this will be a highly used feature. Glad you like it!
I see. I did not realize it was for this purpose. This means the intention was good, and many thanks.
It seems like a pity to waste the whole on/off switch just for this, though, as that is needed for other things. As you said in another post, this “landing default” could also be a preference setting or actually probably a fixed default when you get to that stage of development. I think it follows the same logic and purpose as landing on top, so if people do not complain about landing on top they will probably love this, too Or if not, you could implement a joint preference setting for both - either top/green or bottom/gray?