From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuri Niyazov Subject: org-log-done vs. State Logbook Date: Sat, 3 Jan 2015 00:42:32 -0800 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7KIc-0000rI-8K for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 03:43:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y7KIb-0001eh-7f for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 03:43:06 -0500 Received: from mail-la0-x234.google.com ([2a00:1450:4010:c03::234]:45052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y7KIa-0001eL-V3 for emacs-orgmode@gnu.org; Sat, 03 Jan 2015 03:43:05 -0500 Received: by mail-la0-f52.google.com with SMTP id hs14so16068266lab.39 for ; Sat, 03 Jan 2015 00:43:03 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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.