1.6.2 "...Projects can now appear in Context mode perspectives" oh no!
 

Projects appearing in contexts is new behavior that deviates from the desktop version (1.7.*). The usefulness of my perspectives on my iPhone is diminished. What is most upsetting is that the scope of a project's default context is expanded to apply to the project itself, whereas previously it only applied to new actions. If projects must, going forward, appear in contexts, I would like to see a new project attribute, "Completion Context"; and have default context revert to its previous scope.

[QUOTE=cfrre;76232]Projects appearing in contexts is new behavior that deviates from the desktop version (1.7.*). The usefulness of my perspectives on my iPhone is diminished.[/QUOTE]

If you configure the perspectives to only display available items (rather than all remaining items), does that help? (Projects won't be available until all their actions have been completed.)

Or do the perspectives in question not work as well unless they show all remaining items? (What kinds of perspectives are they?)

[QUOTE]What is most upsetting is that the scope of a project's default context is expanded to apply to the project itself, whereas previously it only applied to new actions. If projects must, going forward, appear in contexts, I would like to see a new project attribute, "Completion Context"; and have default context revert to its previous scope.[/QUOTE]

In the current design, every task (whether a group or an action) has a context. New children within a task inherit their default context from their parent. (This is how inheritance has always behaved: if you had a single action and broke it down into subtasks, the subtasks would start out inheriting the context from their parent.)

But yes, there definitely is a workflow change in this release: groups previously weren't considered actionable themselves (even though you could complete them), so any context you assigned to them previously only affected their children, whereas it now also affects the placement of the group itself in context lists.

I'd like to make the workflow as simple as possible, but not simpler: so please do let me know where this change is causing you friction—we'd like to address that!

Ken, if you have a "waiting for" context which is on hold the restriction to show only available tasks is a no go.
That´s my problem too....
I really dislike the display of projects in context mode (not my kind of understanding context mode)....

If this would be an option like you plan it in the desktop version it´s ok.....

thx

I just remembered something very important! [URL="http://people.omnigroup.com/kc/DebugOmniFocus/HideParentsInPerspectives.html"]The new behavior is configurable.[/URL]

Great!
Thank You!

[QUOTE=Ken Case;76278]I just remembered something very important! [URL="http://people.omnigroup.com/kc/DebugOmniFocus/HideParentsInPerspectives.html"]The new behavior is configurable.[/URL][/QUOTE]

Thanks. I immediately used the option to disable the new behavior. I don't like to see projects in my contexts view, especially since I have sometimes some "open" projects which no longer contain items but which are not yet completed: maybe I'm still thinking about what to put in them, maybe they are projects which get filled intermittently with actions (like the one I have for audio or video conversions: it's often empty, but sometimes I put there tasks I have to perform. I do not like creating a new project every time I have a file to convert).
Maybe what I'm doing is not 100% GTD certified, I don't know, but it works for me. Like the "cumulative" badge in the iPhone version of OF, which I largely prefer to the strictly hierarchical one in the Mac version...
([url]http://forums.omnigroup.com/showthread.php?t=14907&highlight=badges[/url])
:-)

[QUOTE=Ken Case;76236]
But yes, there definitely is a workflow change in this release: groups previously weren't considered actionable themselves [/QUOTE]

It seems to me that not only groups, but also projects are considered actionable here, if they are empty and have a default context at least. IMHO, that does not work so well. :confused: