Flags?! Contexts! Tags?! Do we really need all that? :D Thanks, Dwight, for the idea! I'll look into it as well. :-)
On Monday, December 12, 2016 at 8:48:56 PM UTC-6, Dwight wrote: > > Like Elizabeth, I mark rejected items done, indicating that no further > effort is needed for this item. I have a "Rejected" flag that use for the > same purpose as Elizabeth's "!Cancelled" context > > On Monday, December 12, 2016 at 5:22:48 PM UTC-5, Elizabeth Lindsay wrote: >> >> I created a context called "!Cancelled", add that context, then click the >> checkbox to mark it as done. Then if I'm reviewing my older stuff (i.e. >> closed items), I can tell it wasn't done versus was done. >> >> On Monday, December 12, 2016 at 10:06:21 AM UTC-6, 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 [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/b028d5da-e1bf-4440-b6b0-71feb3938dc0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
