Totally agree. At very least, there should be a notation of this in the User Guide. In both sections that mention "Active Actions," 5.2.1 and 5.3.2, they indicate that future start dates are filtered out. Those sections should have a notation that indicates that this is not the case of "ActiveAction" in the advanced filtering rules.
And there doesn't seem to be a place in the User Guide that explains what ActiveAction actually is, so I'm not sure how the user is supposed to figure this out? I was extremely committed to adopting MLO, and spent many hours going through the User Guide and forums. I really, really wanted to like MLO. But this oversight was incredibly frustrating, wasted a lot of my time, and has left a really bad taste in my mouth. To the point where I've switched to another task management application--even though I already purchased MLO license, cloud sync, and Android app. I hope the developers fix this, because I'd love for MLO to succeed, and I feel things like this are a turn-off for users. On Sunday, May 29, 2016 at 6:02:27 AM UTC-7, Dwight Arthur wrote: > Hi, Andrew, I understand that your problem is fixed. However, I need to > make one more comment just to make this as clear as possible to future > users who may be reading it: > Andrew is totally correct that "Active Actions must not have a start date > or have a start date that has already occurred". This actual issue here is > that the "ActiveAction" test in MLO's Advanced Filtering is misnamed. It > should actually be called "IsOrWillBeActive" and there should be another > test called "IsActive". The current test (ActiveAction, should be > IsOrWillBeActive) tests for six of the seven conditions that could make a > task inactive, it ignores the condition involving start date. This is > necessary to enable views like "Active Next 7 days". The result of this is > that anyone who actually wants to filter for tasks that are actually active > right now as to code ((ActiveAction) AND ((StartDateTime orOrBefore Now) OR > (StartDateTime doesNotExist))) in order to include the start date test > along with the other six tests. If the current version of the test > (ActiveAction) were renamed IsOrWillBeActive then there should be a new > test IsActive that would include the date test. So far there is no > indication that MLO will be changed in this way. > -Dwight > > On Saturday, May 28, 2016 at 5:33:45 PM UTC-4, Andrew Hwang wrote: >> >> Thank you very much, I think that was the problem =). >> >> I found that very misleading because the User Guide explicitly states on >> page 37 that Active Actions must not have a start date or have a start date >> that has already occurred: >> >> Action Actions... >> 3) Tasks without a Start Date, or whose Start Date is today or in the >> past >> >> >> Nevertheless, seems like problem solved--thanks so much! >> >> >> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/bec9c0d1-886b-4b27-ba43-1629cbb2fca6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
