I very like the idea of marking a task as an event, and use it to manager due date or dependency. That's why I have long campaigned for integration of agenda (whatever the way, preferably sync Google Calendar) in order to make such a "event task" dynamic; I mean : if the date has changed in the agenda, it automaticallyit impacts all the tasks that depended on it.
Olivier Le mardi 5 mai 2015 10:10:41 UTC+2, Ian F a écrit : > > Hi. > > Now that Andrey has developed a Calendar View for iOS (a fantastic > feature) and is possibly working on one for Windows and Android, I would > like to add my 2¢ and invite everyone to give their own feedback. I created > a related feature request on UserVoice > <http://mlo.uservoice.com/forums/9235-general/suggestions/7260012-mark-task-as-event-for-calendar> > > but still am not 100% sure if this is the right way to go. > > I think it would be useful to be able to create or mark a task as an " > *event*" (as we do with folders and projects) and to differentiate > between *hard *and *soft* due dates and start dates. The Computed-Score > algorithm should consider these factors by applying higher weights to hard > due dates and events (and also to effort, min time & dependencies > <http://mlo.uservoice.com/forums/9235-general/suggestions/7241670-take-dependencies-and-effort-max-time-into-accou> > ). > > If we are faced with an externally imposed deadline or a date that we > simply must have something done by, then that is a "*hard*" due date. A " > *soft*" due date, on the other hand, could be an aspirational date of our > own choosing to either plan our activity or even to push ourselves to get > something done. If we miss a *soft *due date, it isn't that big a deal, > but if we miss a hard due date then the task is rendered irrelevant. > > Similarly, a "*hard*" start date means we can only do a task after that > date and not before (like having a dependency on a date rather than another > task). A "*soft*" start date could mean that we are simply setting a > reasonable lead time for a task in order to avoid being overwhelmed with > future tasks in our list of currently active tasks. > > Dwight suggested > <https://groups.google.com/d/msg/mylifeorganized/HEpeG4jn3pE/DuA0_uwLLiUJ> > using > the start date as a soft *due* date, however, that would not work unless > you abandon the built-in Active and Available Tasks filters completely and > use advanced filtering instead. If we were to take that approach, tasks we > could be working on now but have a future start date would be excluded by > the Active and Available Tasks filters. > > What do you think? > > Here's my attempt at a view called "Upcoming Events" (which doesn't use > the Active Tasks filter). Ideally, I would like to be able to create a > filter rule that says that the Start Date and the Due Date are on the same > day (or within x hours or days of each other). Unfortunately there are no > filter rule functions that accept two or more fields) : > > > <https://lh3.googleusercontent.com/-IyomsHlrYH4/VUOdeh_b8mI/AAAAAAAAAA4/dTf_dMZVfWY/s1600/upcoming%2Bevents.PNG> > > Ian. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/1b8a0996-c9d5-4aef-a042-8b108a5210b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
