emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Yuri Niyazov <yuri.niyazov@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-log-done vs. State Logbook
Date: Sat, 3 Jan 2015 20:57:29 -0800	[thread overview]
Message-ID: <CACbjG0uTB-5NjPSJuE+Q_Ew=BMb2uHDqgZ_aCu2N-wg4GHuEdg@mail.gmail.com> (raw)
In-Reply-To: <87r3vb9msx.fsf@ericabrahamsen.net>

Thank you. I am already using it, and org-habit really is for habits,
rather than for individual tasks. The closest non-Org analogy I can
think of what I am trying to implement is (for the programmers out
there) the "SCRUM" development methodology. I know it has its
detractors and is quite controversial, but the one aspect of it that I
liked when I was exposed to it is that it required someone to keep
track of how long it took a task, on average, to go from "created" to
"completed" stage.

On Sat, Jan 3, 2015 at 8:45 PM, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Yuri Niyazov <yuri.niyazov@gmail.com> writes:
>
>> Hi everyone,
>>
>>
>>   So, I am trying to learn org-mode and figure out what's best for me.
>> One of the things that I would like to see is how long a TODO task
>> takes to travel through my life, on average from the moment when it is
>> captured, to scheduled, to done. Does something like this already
>> exists?
>>
>> One of the things I learned earlier today from this thread
>> https://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg00112.html
>> was that there's nothing that allows you to log state at the moment of
>> capture, so I created a capture template with a LOGBOOK drawer
>> included with an initial state change, like this:
>>
>> "* TODO %?
>> SCHEDULED: %^t
>> :LOGBOOK:
>> - State \"CAPTURED\"   from \"\"           %u
>> :END:"
>>
>> Now, one of the things that I am finding hard to figure out is what to
>> do at the end: there's both the ability to log when the object is done
>> using org-log-done, and one can also track every state change, which
>> includes the final state change of being done, with LOGBOOK state
>> changes. I am leaning towards turning them both on going forward, but
>> I have a bunch of old tasks, and some of them only have the CLOSED:
>> [timestamp] entry, and some of them only have the -State "DONE" from
>> "TODO" line in Logbook, and I don't know whether to invest the time
>> into fixing up the old entries to mirror the existing ones. The answer
>> to this depends on whether a package for for displaying statistics to
>> me already exists, and if it depends on one of those (CLOSED entry vs.
>> Logbook state changes).
>>
>> I know about clocktable, but clocktable seems to only be for
>> Clocking-in and Clocking-out entries, not across the lifetime of a
>> task.
>
> You could maybe take a look at org-habit? I haven't really used it, so I
> can't tell you about its ins and outs, but it might be useful. On the
> other hand, it seems to be mostly for repeating habits. Dunno what else
> there is...
>
>

  reply	other threads:[~2015-01-04  4:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03  8:42 org-log-done vs. State Logbook Yuri Niyazov
2015-01-04  4:45 ` Eric Abrahamsen
2015-01-04  4:57   ` Yuri Niyazov [this message]
2015-01-04  5:02     ` Yuri Niyazov
2015-01-04  5:19       ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACbjG0uTB-5NjPSJuE+Q_Ew=BMb2uHDqgZ_aCu2N-wg4GHuEdg@mail.gmail.com' \
    --to=yuri.niyazov@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).