From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Millar Subject: Re: Clocktable feature requests Date: Mon, 06 Jul 2015 12:21:13 -0400 Message-ID: <559AAAF9.6000705@verizon.net> References: <87mvz95l09.wl-ded-law@ddoherty.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZC99n-0006mW-LT for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 12:22:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZC99c-0000tY-OP for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 12:22:11 -0400 Received: from vms173019pub.verizon.net ([206.46.173.19]:55656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZC99c-0000j3-Iy for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 12:22:00 -0400 Received: from [192.168.1.59] ([24.39.254.154]) by vms173019.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NR2005PUQRD9WB0@vms173019.mailsrvcs.net> for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 11:21:13 -0500 (CDT) In-reply-to: <87mvz95l09.wl-ded-law@ddoherty.net> 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 Dan, Maybe Tom Marble's timesheet..el is what you are looking for https://github.com/tmarble/timesheet.el As I recall if was discussed on this list awhile ago. Also see his interview with Sacha Chua's interview with Tom http://emacslife.com/emacs-chats/chat-tom-marble.html Hate to say this, but I still haven't tried it myself. Charlie Millar On 07/06/2015 12:05 PM, Daniel E. Doherty wrote: > I typically keep a list of tasks I'm working on in a subtree that is > simply a bunch of subheads that describe the task, like so: > > ,---- > | * Time Records > | ** Review filings for Johnson--Morgan > | CLOCK: [2014-08-27 Wed 09:13]--[2014-08-27 Wed 12:20] => 3:07 > | ** Discussion with Smith re Johnson possible violation > | CLOCK: [2014-08-27 Wed 10:35]--[2014-08-27 Wed 10:55] => 0:20 > | ** Prepare and send demand letter for Johnson > | CLOCK: [2014-08-28 Mon 11:18]--[2014-08-28 Thu 12:20] => 1:02 > | ** Forward summary to Smith following on discussion > | CLOCK: [2014-08-29 Fri 09:35]--[2014-08-29 Fri 09:45] => 0:10 > | ** Receive and review letter from Willy Wonka re demand > | CLOCK: [2014-09-11 Thu 09:38]--[2014-09-11 Thu 10:39] => 1:01 > | ** Prepare reply to Wonka response letter > | CLOCK: [2014-09-11 Thu 10:40]--[2014-09-11 Thu 11:30] => 0:50 > `---- > > I clock in and out of tasks as I work on them. There is typically no > 'SCEDULED' or 'DEADLINE' associated with the tasks. > > I would like to produce a clocktable that works as a passible bill. > > There are two things that make this difficult: > > 1. I would like the clocktable to have a column that indicates the date on > which the activity took place. > > 2. I would like the an optional 'Rate' and 'Charge' columns to be added > > As to 1: > > The timestamp feature almost takes care of 1, except that it will not use the > CLOCK property to set the timestamp. Using the date (optional time) at which > the CLOCK started would work as a good timestamp, and probably better than > something like the SCHEDULED or DEADLINE. If the purpose is to indicate when > the activity occurred, it would seem that the best order for picking the time > stamp would be something like TIMESTAMP, TIMESTAMP_IA, CLOCK (begin), > SCHEDULED, then DEADLINE, that is from more specific to more general. > > As to 2: > > With an option like :rate set to, say, 50, the time column could be converted > to dollars (or whatever currency) at rate * hours. It would also be nice to > have that amount summed in the same way that time is summed by levels now. > > With those items added, the clocktable would be usable as a billing > mechanism. As it is now, it makes a nice start, but requires a lot of > massaging to turn a clocktable into an invoice. > > Any chance of getting these features added? > > Dan Doherty > >