[brooce]

Hi!

I'd appreciate seeing a prioritized feature list for what's still to come in OmniFocus.

Not that you have to listen to us, but it'd be nice to be able to provide some guidance on where you spend your development time...

[Athanasius]

That's a good suggestion. Maybe an alpha roadmap, beta roadmap, 1.0 road map and ultimately a post-1.0 roadmap.

[LizPf]

I'd love this too ... but I worry that the folks who only read half the info provided will begin yammering if a feature is 10 minutes late. Or if feature #2 gets implemented before feature #1. [I won't out the guilty, but I have seen some of this here.]

And again, it would take time away from the actual development.

So I'll happily keep downloading my updates, sending in my feedback forms, and waiting. Though, OmniFolk, if you do have a spare moment ...

--Liz

[michelle]

We're definitely listening to customer feedback. We have over 2000 customers providing us with feedback right now. Many bugs and features have been re-prioritized based on the feedback we have received. We can't provide you with a specific road-map right now, but keep sending us feedback!

Michelle

[Ken Case]

Originally Posted by brooce

I'd appreciate seeing a prioritized feature list for what's still to come in OmniFocus.

Sorry I didn't comment on this sooner! Before we offered our first downloads, we posted our "Known issues" and "Coming soon" lists near the top of the download page.

What would be most useful to us is for all of you to tell us how those lists should change: what features are missing from our "Coming soon" list that you consider essential for 1.0? In your opinion, what bugs and other issues absolutely need to be addressed before we can ship 1.0, and which ones can wait until later?

Thanks!

[HiramNetherlands]

I'd like to see task aliases (called 'cloned tasks' in another thread), i.e. tasks that are part of more than one project. They'd have to be 'hard links', in the sense that editing (and checking off, and even deleting) them edits (checks off, deletes) all their other instances.

Such task aliases would be useful simply because often enough, one particular condition needs to be met for several (unrelated) projects to proceed.

[Ken Case]

Originally Posted by HiramNetherlands

I'd like to see task aliases (in another thread called 'cloned tasks'), i.e. tasks that are part of more than one project.

I certainly see how cloned actions would be useful, but they have all sorts of UI ramifications that would introduce a bunch of new work. (For example, an action can be "available" in one project and "not available" due to dependencies in another, so which one is right? In context view, do we list each clone of the action separately, or do we modify the project column to somehow handle multiple project assignments?)

So we won't be doing cloned actions for 1.0, though we'll certainly consider them for future releases.

[HiramNetherlands]

Originally Posted by Ken Case

I certainly see how cloned actions would be useful, but they have all sorts of UI ramifications that would introduce a bunch of new work. (For example, an action can be "available" in one project and "not available" due to dependencies in another, so which one is right? In context view, do we list each clone of the action separately, or do we modify the project column to somehow handle multiple project assignments?)

So we won't be doing cloned actions for 1.0, though we'll certainly consider them for future releases.

I understand that, and I'll happily wait for a post 1.0 release to include this feature, but without wanting to press the issue, let me try to answer the questions you raise.

Can dependencies arise in one project, where there are none in another, for the very same action, provided the action is well defined, specific, 'atomic', GTD-kosher, so to speak? I think an aliased/cloned action, if it is available in one project, is of necessity available generally. Even if 'Replace tire on car' is not available in sequential project 'Move Furniture', because 'Call friends to ask for help moving furniture' comes first, having the tire replaced as part of a different project won't hurt the 'Move Furniture' project, and it is entirely possible to replace the tire without calling those furniture carrying friends first. Am I overlooking something?

In Context view, I can imagine aliased actions having 'Multiple' as their listed project, while mousing over the word 'Multiple' would reveal all the projects the task is part of.

[brab]

Originally Posted by Ken Case

What would be most useful to us is for all of you to tell us how those lists should change: what features are missing from our "Coming soon" list that you consider essential for 1.0? In your opinion, what bugs and other issues absolutely need to be addressed before we can ship 1.0, and which ones can wait until later?

I'd love to see a "Review Mode" built upon the review frequency and last review (I don't really understand how they are updated right now, and how to use them).

Similarly I'd love a view where I can see the oldest available tasks, to make me decide what I should do about them.

[Ken Case]

Originally Posted by brab

I'd love to see a "Review Mode" built upon the review frequency and last review (I don't really understand how they are updated right now, and how to use them).

You can do this now in Project View by grouping your projects by their Next Review date. This will show you all the projects which you need to review in the next week, month, etc. Select a project, review it, then select "Mark Reviewed" from the Edit menu (Shift-Command-R) or toolbar (if you've added it to your toolbar), or use the Project inspector to enter a specific future review date (and update interval).

You can save this view as a Perspective to easily get back to it later.

Similarly I'd love a view where I can see the oldest available tasks, to make me decide what I should do about them.

In Context view, try grouping your actions by their Added or Changed date. Again, you can save this view as a Perspective to get back to it easily later.

(We do plan to improve Perspectives between now and when we ship, letting you change their titles, switch to perspectives in existing windows rather than always opening new windows, delete individual perspectives rather than deleting all of them at once, etc.)