[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: Day workflow: need your opinion

From: Bernt Hansen
Subject: [Orgmode] Re: Day workflow: need your opinion
Date: Mon, 10 Aug 2009 17:36:00 -0400
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Xavier Maillard <address@hidden> writes:

> Thanks a lot Bernt. This is how I am doing things right now which
> "partially" works for me.
> I need a way to tag a TODO as INTERRUPTED automatically when
> clocking-in a new item through remember.
> Eg:
> Working on task A which is marked as STARTED. Someone calls me
> asking for help. I C-M-r a new clocked item, automatically
> marking previous clocked-in item (task A) as INTERRUPTED.

There is a variable for changing task states when clocking out a task.
Every task that clocks out but isn't finished is essentially

The variable org-clock-out-switch-to-state controls that IIRC but I've
never actually tried that (yet).  I just leave my tasks in a STARTED
state.  Anything for me that is STARTED is interrupted (partially worked
on and unfinished).  My STARTED list tends to be less than 20 tasks
total (13 right now).  I just use my STARTED agenda view to pick up the
in-progress tasks easily and clock one in.

> Even better would be to have something that could clock-out
> automatically when a task hits some tags: WAITING or INTERRUPTED.
> Do you know if it is possible ?

There is a org-after-todo-state-change-hook which you could probably use
to accomplish this.

> Also, while at it: how do you access a "daily report" of what has
> been done and how long it took to do ?

I look at my clock report data in the agenda.  Just pull up a day or
week view and hit R for the report.  You can insert clock reports in
your org files and this is the way I used to do this... but when agenda
reporting came along I abandoned that altogether.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]