[Toadling]

Originally Posted by Omnificus

I cannot understand why Omnigroup chose to make projects and group parents actionable.

I don't think it was an arbitrary decision implemented just to foil your workflow. :-)

For a very long time (maybe since the initial 1.0 release almost 3 years ago) there's been a very vocal group of users advocating for this behavior. I think Omni thought long and hard on this issue and finally decided to do something about it.

Unfortunately, it's virtually impossible to make everyone happy. Personally, I find I'm consistently happier if I remain flexible and don't lock myself into any particular workflow.

-Dennis

[henry]

Can someone summarise why making projects and groups actionable is a good thing.

[whpalmer4]

See Ken's posts http://forums.omnigroup.com/showpost...9&postcount=31 and http://forums.omnigroup.com/showpost...3&postcount=60

[sghiassy]

I've been using OmniFocus since kinkless (2005ish). I love OmniFocus but this new workflow feature of actionable Groups is killing me... I am praying to the OmniGods to at least provide an option to disable this terribleness.

[Brian]

Some example threads for the folks that are helped by the change:

• Show action group in context mode?
• Why does DUE view not support Outlining?
• "I don't know why action groups are distinguished from actions."

That said, folks that don't like the new behavior can disable it under the View menu. "Hide Parent Items" is the one you're looking for. :-)

[patgallant]

I personally like the change. If I'm operating in a context and I finish the last item I have in a project, that project's name shows up in my list. I don't always plan out every step of a project at the start, so this is an opportunity for me to either a) add more actions to the project or b) mark the project as complete without it slipping from my focus.

It seems that the only way to add actions to a project from context view is to double click on it (or use Option+Command+R) right? If I select a project in my context list and try to add a child (Command+}) it beeps at me.

[whpalmer4]

Originally Posted by patgallant

It seems that the only way to add actions to a project from context view is to double click on it (or use Option+Command+R) right? If I select a project in my context list and try to add a child (Command+}) it beeps at me.

Or bring up the quick entry window via your quick entry shortcut or toolbar button. Not ideal if you need to do some rearranging of existing material as you add the new actions, but for just tacking new stuff on at the end (the scenario where the project pops into the context view after all the actions are completed) it works fine.