[Brian]

Originally Posted by brianogilvie

adding tasks to a project when the filter is "Available": in that case, hitting return produces a task that is not visible because, until it has a context, it's not available.

To clarify - both problems you're mentioning here are caused a problem we plan to fix before the app goes final. Filters are always applied immediately. Thus, the general preference not appearing to have any effect.

When you add a new row after we fix this, we won't apply any filters you have active until you finish editing and (I believe) select another row. If the row didn't match your current filter, it would then disappear at that point. (Or not, I suppose, if you then added a child task as your next action...)