From: Malcolm Matalka <mmatalka@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tracking time from one state to another?
Date: Tue, 23 Apr 2019 08:07:44 +0200 [thread overview]
Message-ID: <86tvepckzz.fsf@gmail.com> (raw)
In-Reply-To: <875zr66rol.fsf@geus3064linuxwsm.geus.dk>
Ken Mankoff <mankoff@gmail.com> writes:
> Hi Malcom,
>
> On 2019-04-17 at 14:20 +0200, Malcolm Matalka <mmatalka@gmail.com> wrote...
>> Is it possible in org-mode to track, and report, the duration of
>> certain state transitions in org-mode? In particular, I'm interested
>> in tracking how long it takes me to go from a state that means I'm
>> actively working on an item to it being in a done state?
>>
>> In my case, an item might go from working, to waiting, to working, to
>> done. And in this case I'm only really interested in the last working
>> to done time.
>
> Org doesn't have a built-in feature to turn on/off the clock when you
> change state, as far as I know. But it has the opposite - you can
> change state when you clock in or out of a task.
I don't want to turn on/off the clock when I change state, I want to get
a report on the time between certain state transitions. That
information is stored in the LOGBOOK (assuming one has that turned on).
>
> See section 7 here https://writequit.org/denver-emacs/presentations/2017-04-11-time-clocking-with-org.html#helpful-things
>
> And/or maybe thread here w/ some code https://lists.gnu.org/archive/html/emacs-orgmode//2009-04/msg00315.html
>
> So perhaps you can achieve this by changing your workflow a bit. Instead of changing state, just clock in and have the state set to INPROGRESS. Clock otu and have it set to WAITING. When it is done, it may be a two-step process of setting to DONE and making sure the clock is stopped.
>
> Would this achieve what you're looking for?
Unfortunately no. I need to track the total time I spend in a task for
billing reasons, but what I'm interested in here is how quickly I
complete a task when there are no blockers/dependencies. And the way
that presents itself in my LOGBOOK is the time between the final
transition from NEXT to DONE. Before that, a TODO can go from NEXT, to
WAITING, and back and forth.
>
> -k.
next prev parent reply other threads:[~2019-04-23 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 12:20 Tracking time from one state to another? Malcolm Matalka
2019-04-18 11:25 ` Marcin Borkowski
2019-04-18 15:34 ` Malcolm Matalka
2019-04-19 4:37 ` Marcin Borkowski
2019-04-20 18:55 ` Julius Dittmar
2019-04-22 14:09 ` Malcolm Matalka
2019-04-22 14:27 ` Ken Mankoff
2019-04-23 6:07 ` Malcolm Matalka [this message]
2019-04-23 6:32 ` Ken Mankoff
2019-04-23 9:00 ` Malcolm Matalka
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=86tvepckzz.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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).