Feature Request: Project interdependencies by referencing tasks in other projects

One feature which I desperately need, and which would make OmniFocus 1:1 translatable to a project network diagram, is the ability to specify dependencies between actions in different projects. Such as in the example below:

In my mind, this would work by creating a kind of pseudo-action in the dependent project (Project 2 in this example), that simply references the actual action, wherever it may be. Preferably, the referenced object could be of any type (i.e. project, action group, action), since the only important property to incorporate in the dependent project is the completion status of that object, since that dictates the availability of subsequent actions.

I believe this would be a much appreciated feature addition for many of OmniFocus’ advanced users. I also think it makes a lot of sense from the perspective of OmniFocus’ design ethos, which is largely based on the availability of tasks.

Personally I would see this as moving into the realms of OmniPlan which is I would image is built around complex task and asset dependencies.

Let’s get the automation, and basic collaboration features nailed first which are both on the roadmap. I think the OF time dev budget is going to be pretty tight given OS14 and the new Mac visual design language.

2 Likes

Whilst I can see the logic, this could make the product quite complex and is more for multi person projects than those for individuals.

It’s much easier to add a task in each project pointing to each other with the task in project 2 set to a waiting context so it is on hold, and the task in project 1 telling you to take the other task out of the Waiting context when ready.

1 Like