For me I am a complicated user (that's why MLO suit me good), I would like to see 4 essential date fields in MLO5 as below, so as to fulfill my own productivity approach/style
1. Plan start date (this one is already there in the software: Start date) 2. Plan due date (this is also the same, already there: Due date) 3. Actual start date (this one is missing I believe someone would agree me too ^^" ) 4. Actual due date (once I mark the task complete, so there will be actual completed date) My productivity theory is always plan the start and due date, and these may change according to the needs, especially I work with others. In many years back before I use MLO, I used paper/notebook to track all my tasks, and I log my actual start and due date too. I transferred the details into excel to help analyse my productivity pattern by comparing Plan and Actual dates, weekly and monthly. With these data, I generate chart similar to "Today View" across the timeline to compare what I plan and what actually did. With these reflection, I could have a better understanding of my situation and make improvements. If MLO5 could have *another start date field* (e.g. time logging function), I think I could easily export these details to excel for my own review. Regards, LEW On Friday, 18 May 2018 18:29:09 UTC+8, Christoph wrote: > > Am 18.05.2018 um 10:44 schrieb Stéph: > > Overall, my view is that a better option would be to give all tasks a > > start date (meaning the first date that you /*can* /do them, not the > > first date that you */plan to /*do them > > By the way, this is a general problem with nearly all todo managers - > they don't distinguish between "scheduled date" (date you plan to do a > task) and "start date" (earliest date you can work on the task). Most > don't even distinguish between due date (last date you can work on the > task) and start date, offering only one date field. > > Of course, entering three dates makes everything more complicated. The > challenge lies in creating an interface that makes entering them easy. > Often you don't need to enter three different dates, so there should be > ways to enter only one date, and then differentiate in case of need. And > there should be ways to visualize tasks an move them on a time axis, > i.e. use of drag&drop, user-friendly calendar widgets, sliders etc. It's > time somebody comes up with a simple solution for that problem. > > The worst thing is when fields are used inconsistently. Like in our > example, a start date on one task means earliest date and on another > task means scheduled date. Or an empty start date on one task means "can > start any time" (the task would be considered active), or on another > task means "has not yet started" (the task would be still inactive). > Once fields are used ambiguously, you can't create meaningful dynamic > views any more. Even inside MLO itself there is some inconsistency e.g. > in the formula for the computed score (used for ordering tasks), where > MLO interprets an empty due date as "today", which is usually not what > the user intended. Software should help people more in this regard by > making it crystal clear what every field means, and disambiguating edge > cases like empty dates. > > Solving this problem would be in my view more helpful than any other > improvement or addition of features. > > -- Christoph > > > -- 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/3c73e2e2-e706-4bd1-821f-8333014a2478%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
