It appears when you changed to a new feedback system recently the lengthy discussion around this topic was lost. In a true GTD implementation, a project would only have one "Next Action". In your system this is characterized by the "Next" status.

The problem with this approach is that loading a project with 10-12 tasks that will need to be completed results in 10-12 items that are identified as next to complete. You have suggested in the past that we set them to "Someday" or "Waiting", but both of those also have specific meaning to a GTD practitioner and it's not the same. With 10-12 Next tasks and no way to drag/drop the order of them, the user is forced to read through all of the tasks in each project to find the one which should logically be completed next.

I recommended some time ago that tasks be created with either a status of "Not started", which would let the user set the appropriate next action to "Next". There were several other forum posts that discussed a similar approach the problems it would resolve in great detail. Having either a "Not started" status, or a single user-customizable status and the ability to set it as the default, would alleviate what is for many folks the single biggest shortcoming in your application.

Being able to set a project to sequential instead of parallel (as Nirvana does in its application) is a nicety independent of the next action issue, but it only provides an ordering workaround; it doesn't fully address the problem.

I spent many, many hours over several months evaluating several task management platforms for a replacement to the GTD application I have been using since 2007. While there are a couple other improvements I would make to your application, this is the only one that is actually a pain point for me, and it is for other folks as well.

I sincerely hope you'll consider this feature in the near future. I appreciate your product.