From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subhan Michael Tindall Subject: Re: Clocktable feature requests Date: Tue, 07 Jul 2015 00:20:03 +0000 Message-ID: References: <87mvz95l09.wl-ded-law@ddoherty.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01493e7c61ab0e051a3dfc4e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44187) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCGcU-0000aq-29 for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 20:20:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZCGcS-0004eq-5l for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 20:20:17 -0400 Received: from mail-la0-x229.google.com ([2a00:1450:4010:c03::229]:36492) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCGcR-0004dW-KX for emacs-orgmode@gnu.org; Mon, 06 Jul 2015 20:20:16 -0400 Received: by lagc2 with SMTP id c2so174128276lag.3 for ; Mon, 06 Jul 2015 17:20:13 -0700 (PDT) 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: "Daniel E. Doherty" , Org Mode Mailing List --089e01493e7c61ab0e051a3dfc4e Content-Type: text/plain; charset=UTF-8 On Mon, Jul 6, 2015, 9:07 AM 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 2 should be fairly straightforward with the judicious application of :formula to include a #tblfm style calc line in the header to do your calculations --089e01493e7c61ab0e051a3dfc4e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Jul 6, 2015, 9:07 AM=C2=A0Daniel E. Doherty <ded-law@ddoherty.net> 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] =3D>=C2=A0 3:07<= br> | ** Discussion with Smith re Johnson possible violation
| CLOCK: [2014-08-27 Wed 10:35]--[2014-08-27 Wed 10:55] =3D>=C2=A0 0:20<= br> | ** Prepare and send demand letter for Johnson
| CLOCK: [2014-08-28 Mon 11:18]--[2014-08-28 Thu 12:20] =3D>=C2=A0 1:02<= br> | ** Forward summary to Smith following on discussion
| CLOCK: [2014-08-29 Fri 09:35]--[2014-08-29 Fri 09:45] =3D>=C2=A0 0:10<= br> | ** Receive and review letter from Willy Wonka re demand
| CLOCK: [2014-09-11 Thu 09:38]--[2014-09-11 Thu 10:39] =3D>=C2=A0 1:01<= br> | ** Prepare reply to Wonka response letter
| CLOCK: [2014-09-11 Thu 10:40]--[2014-09-11 Thu 11:30] =3D>=C2=A0 0:50<= br> `----

I clock in and out of tasks as I work on them.=C2=A0 There i= s typically no
'SCEDULED' or 'DEADLINE' associated with the tasks.

I would like to produce a clocktable that works as a passibl= e bill.

There are two things that make this difficult:

1. I would like the clocktable to have a column that indicat= es the date on
=C2=A0 =C2=A0which the activity took place.

2. I would like the an optional 'Rate' and 'Char= ge' 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.=C2=A0 Using the date (optional time) a= t which
the CLOCK started would work as a good timestamp, and probably better than<= br> something like the SCHEDULED or DEADLINE.=C2=A0 If the purpose is to indica= te when
the activity occurred, it would seem that the best order for picking the ti= me
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 c= ould be converted
to dollars (or whatever currency) at rate * hours.=C2=A0 It would also be n= ice to
have that amount summed in the same way that time is summed by levels now.<= /p>

With those items added, the clocktable would be usable as a = billing
mechanism.=C2=A0 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




2 should be fairly straightforward with the judicious applic= ation of :formula <formula> to include a #tblfm style calc line in th= e header to do your calculations

--089e01493e7c61ab0e051a3dfc4e--