From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Track time on day-to-day basis
Date: Fri, 25 Nov 2016 12:59:56 +0100 [thread overview]
Message-ID: <20161125115956.GE4967@volibear.adamsinfoserv.com> (raw)
In-Reply-To: <87y407q25y.fsf@fastmail.fm>
On Fri, Nov 25, 2016 at 11:33:45AM +0100, Joost Kremers wrote:
> I've come into the need to track the time I'm working on a
> particular project, which is great with Org, but I also need to
> report the tracked time on a day-to-day basis. This seems somewhat
> less straightforward to do. I realize I can generate a report
> limited to today by specifying `:block today`, but that only gives
> me the time clocked today. What do I do when I want to get a
> day-to-day overview of the time spent on a project? Do I need to
> maintain another table by hand, in which I copy the time
> calculated by `org-clock-report` at the end of each day? Or is
> there a better method?
Joost,
I keep a time stamped journal of all of my projects. Every time I
switch tasks I add in an inactive timestamp, and I make sure each TODO
item is timestamped on close.
Then I can open the agenda for just that file, enter logbook mode, and
enable inactive timestamps. This gives me a great detailed timeline as
to what occurred and when.
It does not tally hours automatically, but I have previously used it
to justify hours in my consulting practice.
> BTW, just looking at the LOGBOOK drawer doesn't work, because I
> may clock in and out of a project several times a day.
Not the drawer, logbook mode. "l" in the agenda.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2016-11-25 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 10:33 Track time on day-to-day basis Joost Kremers
2016-11-25 11:59 ` Russell Adams [this message]
2016-11-25 14:32 ` ngreply
2016-11-27 20:57 ` Joost Kremers
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=20161125115956.GE4967@volibear.adamsinfoserv.com \
--to=rladams@adamsinfoserv.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).