Umberto: There have been a lot of discussions around the concept of using MLO to _schedule_ tasks; so far the discussion has not yet yielded (in my opinion) a clear vision of something that could be done that would be helpful without making MLO _less_ usable or valuable to a lot of its current users. The developers have signaled an intention to do something about the request for a calendar view, but so far there’s no kind of clarity about what they can or will do.
You seem to be trying to advance a vision that compromises between needed functionality and the need to avoid complexity and that’s a good step. If you read up on the discussions that have gone before and see where the conflicts lie, maybe you could enhance your vision to the point where people would recognize it as a feasible solution, and that might bring us a step closer to seeing it happen. To learn more about the previous discussions I think you should search this forum and also http://mlo.uservoice.com and look for “calendar”. To me one of the most difficult points is that dates mean different things and the meanings get confused. The most intuitive meaning is that start date is when you schedule to start working on a task and end date is when you schedule to finish it. A more GTD-oriented meaning has start date as the first date on which it’s possible or meaningful to work on a task, and due date as the last day on which it’s possible or meaningful to do it. For example, if I fail to run my backups tonight, the opportunity is gone. There’s no point in running it twice tonight in an attempt to catch up. So I think we need four dates: GTD beginning, scheduled start, scheduled end and GTD due. But they would need better, less confusing names. I used to schedule my tasks. I spent a lot of time tweaking the schedule that could have been spent getting things done. I only schedule a very few tasks now, but I appreciate that people trying to give an estimate to a client are facing different issues. I hope that you are able to make suggestions that help us through this. -Dwight From: [email protected] [mailto:[email protected]] On Behalf Of Umberto Uderzo Sent: Monday, May 06, 2013 9:34 AM To: [email protected] Subject: Re: [MLO] Using effort time to get a due date "projection"? Yes, i understand that MLO currently doesn't understand such concepts. As i premised, i'd like also a "guessing", so just telling MLO what are the working days in a week should be nice for me. I don't pretend to get a full calendar with holidays and so on. And i can accept also to express actions in days and not hours (i rarely work with something that has a finer granularity) I know that opening MLO to such practice may lead the product to an unwanted complexity. Just wondering if in future this can be achieved (i used MLO for years and really i didn't find anything better to handle freelancer scheduling, but other products and MLO both "fail" (big word) handling this with this issue, that for me is becoming crucial). Maybe there are online tools that can do that, but i hate online tools :) Thank you! Il giorno venerdì 3 maggio 2013 05:34:48 UTC+2, Lisa S ha scritto: I don't think it is possible. It sounds like you are looking more for project management, which is not an area that MLO tries to cover. MLO doesn't understand concepts like number of hours in a work week (or even, what is a work week). On Thu, May 2, 2013 at 1:57 AM, Umberto Uderzo <[email protected] <javascript:> > wrote: Hi all! I'm trying to figure out if there is (will be) some way to use the effort time to get a future projection of end date for a group of activities. What i'm looking for is to maintain a list of to do activities where there is no start/end date set, but only the effort in time it will take. By considering the working days in a week i'm interested to get some kind of "guessing" of when each activity should be completed. I need then to be able to resort the activity list (because of priority changes) then get an instant recomputing of the "guessed" end date without doing it manually. I know it's impossible to get a precise result because there are lots of variables to consider, but a guessing is ok for me. I need something that i can use to explain my customers "what if" we change some priority. Is it possible? Or is it ehough interesting to be implemented in future? Thank you! Umberto -- 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] <javascript:> . To post to this group, send email to [email protected] <javascript:> . Visit this group at http://groups.google.com/group/mylifeorganized?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- Lisa _____ Lisa Stroyan, mailto: [email protected] <javascript:> -- 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 http://groups.google.com/group/mylifeorganized?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/mylifeorganized?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
