That could work. I'm aware of how universal the "completed" state is,  
so I'm not saying we should have an entirely separate "third" state.  
The user should be aware that the task *wasn't* actually completed, is  
all.

However, from the interface perspective, it should be possible to auto- 
mark it as completed when the user tags it as dropped - rather than  
having to perform two separate clicks.

As for the term: "cancelled", "dropped", "not progressed" are all  
possibilities.



D

(Another reason is sometimes I create a task, cancel it for some  
reason, and then a few months later, add it again, forgetting that I  
decided it wasn't a good idea. Being able to add the reason and  
"cancel" it is useful as an audit trail, of sorts.)





On 13 Oct 2009, at 08:06, Susanne Araf <[email protected]> wrote:

> How about marking it as completed and flagging it with a special  
> "dropped" flag?
>
> 2009/10/13 Damian Skeeles <[email protected]>
>
>
> +1: I have to admit, I've always missed this functionality.
>
> The task may contain useful information in the notes field, so I don't
> want to delete it. But I never actually completed that task, so
> clicking "completed" is wrong.
>
> Moving to a "dropped" folder also doesn't work, because you then lose
> it's place in the hierarchy. A good example is my "Work/Clients"
> folder. I want to keep the tasks for each client in the same place. I
> want to keep the notes for that task. But if they cancel that
> particular task, I don't want to just delete it.
>
> On 13 Oct 2009, at 04:51, "Mr. Analogy" <[email protected]> wrote:
>
> >
> > Have you considered creating a top level folder called "Dropped" and
> > moving those tasks to that folder?
> >
> > (That way they're still there, but they're not cluttering your
> > "living" tasks)
> >
> > (In GTD this would be called "Maybe Do" (since if you truly knew  
> you'd
> > NEVER do them I'd guess you'd delete them)
> >
> > -Clay
> >
> > On Oct 6, 8:19 pm, Dan <[email protected]> wrote:
> >> One of the hidden consequences of keeping a large list of projects
> >> and
> >> todos in one program is that is also works as a personal journal. I
> >> find this particularly important as I can then export one month's
> >> completed to dos that do not have the context 'routine' to an excel
> >> file for permanent archiving purposes.
> >>
> >> For that purpose, I miss a 'dropped' function of todos that I have
> >> decided not to do after all. I would like them to be included in my
> >> archive of todos but if I delete them in MLO I won't have this
> >> functionality. As for formating, since both greyed out and crossed
> >> out
> >> are used maybe an icon with a large red D would work. Otherwise a
> >> dotted crossed-out would also be a nice visual clue to see the
> >> dropped
> >> tasks.
> > >
>
>
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mylifeorganized?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to