[ryantate]

OK it looks like this has been asked about in years past, including in the thread "Feature Request: Subprojects/Action Groups in Projects breadcrumb" and "action groups don't appear in context views." (I tried searching before I posted, but not with Google.)

There is an "official" solution to this -- Ken mulled in 2007 that perhaps action groups should "show up in context view when their children are complete" and sure enough in the 1.8 nightlies there's this feature:

Groups, Projects, and Inbox items now show up in Context lists, Due lists, and Flagged lists. When actions are sorted by project, parent items follow their children (which is the natural order for completing them). Single Action Lists are not actionable, and do not appear in Context lists.

This is really not a solution at all if you're using Action Groups as subgroups;

• my task names would still make no sense since we don't get action group breadcrumbs in Context view AND
• the name of the Action Group in my case ("Find gaming expert") is not always a task unto itself.
• And even if I made all Action Group names into tasks (not sure this would work), there's not yet a way to assign context to the Action Group so it doesn't show up in a Perspective unless you have "No Context" selected.

Another thing Ken suggested was to turn Action Group into Projects. This then implies the parent Project should be a folder. Two problems:

• Project tasks that weren't in action groups now need to become their own single-action projects which is silly and
• If you drag an action into a folder, OmniFocus helpfully converts it into a Project and STRIPS all context information from it. Oy.
• Folders do not have the ability to specify sequential vs parallel the way Projects and Actions Groups do so you lose information.

Basically what needs to happen is that Action Groups need to become full fledged nested Projects. In Context view, Sub project names would be displayed with full breadcrumb trail showing all parent projects to the right of one another. OmniGroup could then nuke the whole concept of Folders and use parent Projects in their place (why not?). Then you'd end up with ONE type of object where you once had THREE. Which makes the software easier to learn.