From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: How to estimate effort by week? Date: Mon, 28 Nov 2011 13:43:15 -0500 Message-ID: <87pqgcccl8.fsf@norang.ca> References: <4EC672D3.70402@googlemail.com> <8762ihs864.fsf@sbs.ch> <4EC68D12.5050509@googlemail.com> <87r514gmap.fsf@norang.ca> <4ED379E5.2000002@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:47201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RV6Av-0006IX-HY for emacs-orgmode@gnu.org; Mon, 28 Nov 2011 13:43:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RV6At-0008UT-S1 for emacs-orgmode@gnu.org; Mon, 28 Nov 2011 13:43:33 -0500 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:26340) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RV6At-0008Hq-Lp for emacs-orgmode@gnu.org; Mon, 28 Nov 2011 13:43:31 -0500 In-Reply-To: <4ED379E5.2000002@googlemail.com> (Christoph LANGE's message of "Mon, 28 Nov 2011 13:09:09 +0100") 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: Christoph LANGE Cc: Christian Egli , emacs-orgmode@gnu.org Christoph LANGE writes: > Hi Bernt, > > thanks a lot for your advice. Sorry, but it took some time until I > found the time for trying it. I think I understood how it works. > Below I just have some minor questions. Hi Christoph, The delay is not a problem at all. > > 2011-11-19 16:32 Bernt Hansen: >> Is this to help limit you to that time per week or for estimating? > > Indeed I was interested in limiting the time that I spend on some task. > >> For limiting you can set up something like this: >> >> --8<---------------cut here---------------start------------->8--- >> * STARTED Some task > ^^^^^^^ > > OK, so this example uses another TOOD keyword, which I haven't had > before. I understand that your example also works without introducing > a new state, but I'm not yet sure what TODO states I need to use this > feature most efficiently. See below for a more specific question > about that. Yes, I use STARTED as a todo keyword and it gets automatically set when I clock in the task. My setup details are at http://doc.norang.ca/org-mode.html in case you want all the gory details. > >> SCHEDULED:<2011-11-21 Mon +1w> >> :LOGBOOK: >> - State "DONE" from "STARTED" [2011-11-19 Sat 10:27] > > If I understand correctly, this mainly follows the habit tracking > documented on the info page "Tracking your habits" =E2=80=93 right? > No this isn't a habit because it doesn't have a STYLE property. It's just a regular repeating todo task. A habit needs a repeater and a STYLE property with a value of 'habit'. >> CLOCK: [2011-11-19 Sat 10:25]--[2011-11-19 Sat 10:27] =3D> 0:02 >> CLOCK: [2011-11-19 Sat 09:28]--[2011-11-19 Sat 10:27] =3D> 0:59 >> :END: >> :PROPERTIES: >> :Effort: 1:00 >> :LAST_REPEAT: [2011-11-19 Sat 10:27] >> :END: >> Limit work to 60 minutes per week >> Let it repeat for next week >> --8<---------------cut here---------------end--------------->8--- >> >> where the task repeats at some interval (weekly since you want to work >> up to 1 hour per week on this task). When you clock in the task the >> modeline shows your current clocked minutes on the task _since your last >> repeat_. > > OK, that's basically what I wanted to achieve, and it's very nice that > the clocked minutes are also shown in a warning face here when I > exceed the limit. It works for me :) > >> Set your Effort property to the limit you want for the task for the >> interval and set your repeat to the size of your interval (1 hour per >> week in this case) >> >> So when you reach the limit of 1 hour (in this case) you mark the task >> DONE which stops the clock and rescheduled the task to the next repeat >> date. > > More realistically I won't do that after one hour, but continue > working on that task (with a guilty conscience), and then mark it DONE > around the end of the week ;-) I don't always stop when I go over either - but my clocked time is shown with a bright red background I can't miss on the modeline and everytime I clock in the task (ie capture something clocks in the capture task and returns to this overrun task) my siren sound is played so it's very obvious. > > OK, I see that marking such a task as DONE does not actually leave it > in the DONE state but takes it back to the first TODO state. When you mark a TODO task DONE (or CANCELLED or any other done-state keyword it cycles back to TODO or to a specific state you specify in a property REPEAT_TO_STATE) > So far I had the TODO sequence "TODO DELEGATED | DONE CANCELLED" and > tried to extend it to "TODO DELEGATED STARTED | DONE CANCELLED", but > that would take my repeating task back to "TODO" instead of "STARTED" > after marking it DONE. I think a separate sequence of states would > make more sense; maybe "STARTED | RESTARTED"? If you want to force the state to STARTED then add a property like this :PROPERTY: :REPEAT_TO_STATE: STARTED :END: Regards, Bernt