Re: logging transitional states

["Eddward DeVilla" <eddward@gmail.com>]

I have also wished for other 'Done' type states.  Currently I mark
them all DONE and if there is something interesting about the
'Done-ness' of it I add that as a tag such as :SCRATCHED: :CANCELED:
or :REJECTED:.  I haven't found it to be much of a problem, but I've
wondered if it would be difficult to do sequential TODOs where the
last item could be a list of DONE states.

   WAIT PLANNING WORKING TESTING (DONE SCRATCHED)

For that matter, having different sequences could be useful.

   TODO (DONE NOPE)
   WAIT PLANNING WORKING TESTING (COMPLETE SCRATCHED)
   REPORTED ANSWERED

This would just complicate things, but it came from me trying to find
a Todo scheme that would be flexible enough to handle all the
different kind of Todo's I deal with in one set of agenda files.  I've
found it easier to have a minimal set of Todo types and tags to
describe unique circumstances.  Anything interesting about a Done
project is a tag.  Blocking factors are tags.  I've also considered
Todo types to be specially treated tags and recent changes to
searching make that illusion a little easier to maintain.

Edd

On 12/18/06, Daniel J. Sinder <djsinder@gmail.com> wrote:
> Just to add a related idea which may be relevant to a new extension:
>
> Even for 'type' TODO keywords, they are asymmetric.  There may be
> any number of keywords that essentially mean 'to do', but only one
> (DONE) that means 'done.'
>
> I occasionally have TODO items that become moot or otherwise
> uninteresting, but I want a record of the fact that they were
> considered for action.  For these, I don't want to remove the 'TODO'
> keyword altogether.  Rather, I could have keywords such as
> WITHDRAWN, CANCELLED, SCRAPPED, etc.  These items are no longer
> things I need 'to do', nor are they truly 'done' (i.e., the task was
> not completed), but I might want to keep them with a record (e.g., a
> closing note) of why I scrapped the idea/plan.
>
> So, combined with Dmitri's suggestion, I guess I'm suggesting that
> TODO keywords should be assigned one of 3 mutually exclusive categories:
> 1. Nothing done yet
> 2. Transitional -- Action taken, but not yet done; in-progress
> 3. Nothing left to do (whether truly 'done' or not)
>
> Anything in category 2 or 3 would be eligible for completion
> logging.  Anything in category 3 would not appear in agenda view
> TODO lists, but could still be found via a TODO keyword search.
>
> In an org file, they could be grouped like this:
> #+TYP_TODO: {TODO NEXT MAYBE} {ORDERED PAYED RECEIVED} {DONE
> WITHDRAWN SCRAPPED}
>
> Dan
>
> Carsten Dominik wrote:
> > Currently there is not, but this looks like a useful extension.
> >
> > Forthcoming, some time next year.
> >
> >
> > - Carsten
> >
> > On Dec 18, 2006, at 13:59, Dmitri Minaev wrote:
> >
> >> Hi,
> >>
> >> I use org-mode with TODO keywords denoting workflow states. E.g., when
> >> tracking purchases, I set the keywords to:
> >>
> >> #+SEQ_TODO: TODO ORDERED INVOICE PAYED RECEIVED SENT
> >>
> >> Is there a way to log the dates not only for the completion (SENT
> >> state), but also for all transitional states?
> >>
> >> Thank you.
> >>
> >> --
> >> With best regards,
> >> Dmitri Minaev
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>