Recording results of TODO items

Recording results of TODO items

[William Kunkel]

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

Is there a standard way to record the outcomes of certain TODO items? For
example, I had a TODO item to research and come to a decision about part of
the architecture of a software project I'm starting, and I'd like to record
the result of that TODO item, that is, the decision that I made. I found
"closing notes" for TODO items, but that's an option that applies to all
TODO items and seems more intended for brief remarks (to me, at least). Is
using the closing notes functionality my best bet, or is there something
better?

Thanks,
Will

[-- Attachment #2: Type: text/html, Size: 623 bytes --]

Re: Recording results of TODO items

[Eric Abrahamsen]

William Kunkel <will@wkunkel.com> writes:

> Is there a standard way to record the outcomes of certain TODO items?
> For example, I had a TODO item to research and come to a decision
> about part of the architecture of a software project I'm starting,
> and I'd like to record the result of that TODO item, that is, the
> decision that I made. I found "closing notes" for TODO items, but
> that's an option that applies to all TODO items and seems more
> intended for brief remarks (to me, at least). Is using the closing
> notes functionality my best bet, or is there something better?
>
> Thanks,
> Will

I do usually use the logging/notes functionality, but if you need more
text, why not just make it the body of the TODO? A TODO is a heading
like any other, you can just put a description of the outcome underneath
it. If that gets unwieldy, separate the bits into multiple sub-headings,
and/or make the TODO itself one smaller part of a larger TODO.

Re: Recording results of TODO items

[William Kunkel]

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

I could well add it in a sub-heading under the TODO, I was just curious if
there was a built-in org-mode way that I ought to be using instead of
rolling something of my own.

Cheers,
Will


On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen
<eric@ericabrahamsen.net>wrote:

> William Kunkel <will@wkunkel.com> writes:
>
> > Is there a standard way to record the outcomes of certain TODO items?
> > For example, I had a TODO item to research and come to a decision
> > about part of the architecture of a software project I'm starting,
> > and I'd like to record the result of that TODO item, that is, the
> > decision that I made. I found "closing notes" for TODO items, but
> > that's an option that applies to all TODO items and seems more
> > intended for brief remarks (to me, at least). Is using the closing
> > notes functionality my best bet, or is there something better?
> >
> > Thanks,
> > Will
>
> I do usually use the logging/notes functionality, but if you need more
> text, why not just make it the body of the TODO? A TODO is a heading
> like any other, you can just put a description of the outcome underneath
> it. If that gets unwieldy, separate the bits into multiple sub-headings,
> and/or make the TODO itself one smaller part of a larger TODO.
>
>
>

[-- Attachment #2: Type: text/html, Size: 1801 bytes --]

Re: Recording results of TODO items

[William Kunkel]

[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]

Alright, I'll just do my own thing then, I suppose. Thanks!

On Tue, Apr 15, 2014 at 10:48 PM, Eric Abrahamsen
<eric@ericabrahamsen.net>wrote:

> William Kunkel <will@wkunkel.com> writes:
>
> > I could well add it in a sub-heading under the TODO, I was just
> > curious if there was a built-in org-mode way that I ought to be using
> > instead of rolling something of my own.
>
> Ah, no -- I think the state-change note is about as built-in as it gets...
>
> > Cheers,
> > Will
> >
> >
> > On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen <
> > eric@ericabrahamsen.net> wrote:
> >
> >     William Kunkel <will@wkunkel.com> writes:
> >
> >     > Is there a standard way to record the outcomes of certain TODO
> >     items?
> >     > For example, I had a TODO item to research and come to a
> >     decision
> >     > about part of the architecture of a software project I'm
> >     starting,
> >     > and I'd like to record the result of that TODO item, that is,
> >     the
> >     > decision that I made. I found "closing notes" for TODO items,
> >     but
> >     > that's an option that applies to all TODO items and seems more
> >     > intended for brief remarks (to me, at least). Is using the
> >     closing
> >     > notes functionality my best bet, or is there something better?
> >     >
> >     > Thanks,
> >     > Will
> >
> >     I do usually use the logging/notes functionality, but if you need
> >     more
> >     text, why not just make it the body of the TODO? A TODO is a
> >     heading
> >     like any other, you can just put a description of the outcome
> >     underneath
> >     it. If that gets unwieldy, separate the bits into multiple
> >     sub-headings,
> >     and/or make the TODO itself one smaller part of a larger TODO.
> >
> >
>
>
>

[-- Attachment #2: Type: text/html, Size: 2704 bytes --]

Re: Recording results of TODO items

[Eric Abrahamsen]

William Kunkel <will@wkunkel.com> writes:

> I could well add it in a sub-heading under the TODO, I was just
> curious if there was a built-in org-mode way that I ought to be using
> instead of rolling something of my own.

Ah, no -- I think the state-change note is about as built-in as it gets...

> Cheers,
> Will
>
>
> On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen <
> eric@ericabrahamsen.net> wrote:
>
>     William Kunkel <will@wkunkel.com> writes:
>    
>     > Is there a standard way to record the outcomes of certain TODO
>     items?
>     > For example, I had a TODO item to research and come to a
>     decision
>     > about part of the architecture of a software project I'm
>     starting,
>     > and I'd like to record the result of that TODO item, that is,
>     the
>     > decision that I made. I found "closing notes" for TODO items,
>     but
>     > that's an option that applies to all TODO items and seems more
>     > intended for brief remarks (to me, at least). Is using the
>     closing
>     > notes functionality my best bet, or is there something better?
>     >
>     > Thanks,
>     > Will
>    
>     I do usually use the logging/notes functionality, but if you need
>     more
>     text, why not just make it the body of the TODO? A TODO is a
>     heading
>     like any other, you can just put a description of the outcome
>     underneath
>     it. If that gets unwieldy, separate the bits into multiple
>     sub-headings,
>     and/or make the TODO itself one smaller part of a larger TODO.
>    
>