I know that it is not policy to share roadmaps/futures, but I also know that I've seen posts from as long as 2 years ago that mention that task dependency is on your to-do list. Could you at least maybe share if it's on your current @work context or if it's just one of those "someday/maybe" kind of things? :)

I would also like to know this. It seems to have been on your list for a while now.

Not that I want to argue with you all - I'd rather not, and if this is what you would like to have, then that is perfectly fine with me. But just in case you haven't thought about it, you can think of task dependencies as stages of progression rather than as strict dependencies.

For example, you could use the Status field for this, which is what I do: The things you need to do now are "Next Actions". The ones that are doable and will follow are "Active", and so on.

This manual promotion has some advantages having to do with the fact that it is often possible, from the individual project's point of view, to do several things in parallel, but you may not have the time, from an overall point of view, to put more than a certain amount of time into each project. By manually reviewing and promoting taks, and occasionally demoting some, you can balance your efforts between your different projects depending on your overall workload.

+1 for me to. I am trying to advise our organisation (35 staff) and our or will pay for each staff member but this is the deal breaker for us. Some kind of idea would be helpful cause the Mac fanboys in the organisation are pushing for Omnifocus... Ballpark ETA?