Like others have mentioned, I also plan to use contexts for this purpose, once I get to set up a proper review process. And use "complete" to get them out of the way for now.
There are certain tasks I want out of the way - cancelled or suspended one way or another but this can be for different reasons. Sometimes I just had to rethink it because I got wiser and it becomes a different project or at a much later time. Other times, I didn't make it because I procrastinated and missed the opportunity. That's another thing I'd want to follow up on. On Monday, 12 December 2016 17:06:21 UTC+1, c.k. lester wrote: > > How do you mark a task at "Won't Be Done" or similar? This is primarily > used in software development management, where an assigned enhancement or > bug fix or something is on the task list, but, ultimately, the programmer > decides it won't be done for one reason or another. Instead of marking is > as "Done," there is a "Won't Do" or "Rejected" status. Is that available > for MLO? > > -- 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 mylifeorganized+unsubscr...@googlegroups.com. To post to this group, send email to mylifeorganized@googlegroups.com. 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/09ba3c65-1c19-4573-9f9c-3219fd79093a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
