Marking as "Won't Do"

[c.k. lester]

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?

[Elizabeth Lindsay]

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.

[Dwight]

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

[c.k. lester]

Thanks for the idea, Elizabeth! What's the difference between having a '@' or a '!' in front of the context? Can I put anything there?

[c.k. lester]

Flags?! Contexts! Tags?! Do we really need all that? :D

Thanks, Dwight, for the idea! I'll look into it as well. :-)

[Stéph]

I use prefix contexts with @ and ! - It helps to sort them into an order which makes sense to me (putting !call ahead of all my @contexts).

Regarding your original question, I use "-superseded" as my tag for "won't be done". I also have an automatic formatting rule to put a little, dark red "x" icon at position 0 for all superseded items. That puts that cross just alongside the task checkbox (as per the attached screenshot).

Stéphane

[Lasse Pedersen]

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.

[MOK | MATSURU]

In GTD, projects or tasks that you decided not to do = completed, coz you have decided not to do & there is no more action required. 

To differentiate these projects/tasks from the actual completed tasks, I put a [ ✘cancelled ] prefix at the beginning of the task name. Then, check it off as complete. 

Hope this is helpful :-) 

--
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+unsubscribe@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.