in my workflow I often end up with a lot of nested subtasks, sometimes many levels deep:
main task
subtask
subsubtask
etc.
I develop these (sub)tasks during my work, but they are still subtasks of the main task rather than tasks by themselves.
When I flag a main task, I expect to appear it in a Flagged perspective, not its subtasks. OF does exactly opposite: flagging main tasks generates hundreds of sub-tasks in the flagged perspective, without the main task on top. I understand that this is probably due to “action group” architecture, but at the end of the day, a very important Flagged perspective is at the moment useless to me…
Do you know any workaround or solution to this problem? The perfect solution would be a Flagged view with only Tagget parent flags (action groups) without subtasks. I imagine it can be achieved either by the option of NOT inheriting a flag by children tasks, or the ability to group subtasks in the Flagged view under the parent (main) tasks,
This has just been added as a feature in the most recent TestFlight versions of OmniFocus 4. I haven’t had a chance to play with it extensively, but it looks promising!
Just for the record, some of us depend on the current behavior for our workflows. Hopefully, if this is implemented it will be as an option rather than a change in behavior.