From: Ihor Radchenko <yantar92@gmail.com>
To: Russell Adams <RLAdams@adamsinfoserv.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Alternatives to clocking in/out for reporting time
Date: Fri, 08 Jul 2022 15:02:00 +0800 [thread overview]
Message-ID: <87let42il3.fsf@localhost> (raw)
In-Reply-To: <Yrxo6D9Eq8mOjRx4@tahm>
Russell Adams <RLAdams@adamsinfoserv.com> writes:
> I find Org's clocking to be too detailed, and that it doesn't play
> well with dynamically organized hierarchies of notes. I frequently
> create and close subtasks, or switch parts of the tree. Clocking each
> one is too much overhead, and too granular. I don't need to provide
> down to the minute reports of each item. It also doesn't appear to
> allow rounding of values, so I still have to adjust the results.
>
> What I envision is a way to count items in the agenda view to produce
> a time report. Counting any inactive timestamp as 15 minutes, where if
> a half hour or more is logged I round up to bill the hour. Closed TODO
> items should count toward billing that whole hour. Clearly this should
> be customized.
>
> The point is that I'm not worried about accounting time by task,
> instead I'm aggregating tasks into accounting by whole hours.
>
> I'm looking at org-element, and it appears I'd have to do my own
> agenda style scan of the whole tree to find items to classify by
> hour. While I'm somewhat proficient at elisp, that sounds like a steep
> wall to climb.
>
> Is there an iterative way to review items in an agenda view so I can
> do the math to produce a report?
You may hook into timestamp insertion/todo-state change functions and
accumulate the "time" into headline properties.
I did something conceptually similar in
https://github.com/yantar92/emacs-config/blob/master/config.org#bonuspenalty-based-time-management
Hope it helps.
Best,
Ihor
next prev parent reply other threads:[~2022-07-08 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:59 Alternatives to clocking in/out for reporting time Russell Adams
2022-06-29 21:26 ` Tim Cross
2022-06-29 22:09 ` Russell Adams
2022-06-30 2:11 ` Samuel Wales
2022-06-30 2:12 ` Samuel Wales
2022-06-30 8:57 ` Russell Adams
2022-06-30 22:32 ` Samuel Wales
2022-07-08 7:02 ` Ihor Radchenko [this message]
2022-07-08 8:10 ` Russell Adams
2022-07-09 4:00 ` Ihor Radchenko
2022-07-09 12:44 ` Russell Adams
2022-07-10 9:30 ` Ihor Radchenko
2022-07-10 23:09 ` Samuel Wales
2022-07-10 12:26 ` Olaf Dietsche
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87let42il3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.