clocking ongoing items

clocking ongoing items

[Rainer Stengele]

Hi all!

I wonder how others are clocking ongoing isues, which are not really todos but more like "issues" collecting clocked time for work done regularly.
Example: Reading mail and organising daily priorities of tasks.
This "todo" will not finish very soon.
I want this item to be clocked daily but do not want it to look like a standard todo.
How do others handle this? I remember Bernt once had a tag "ONGOING" which he dropped again.

Cheers,
Rainer

Re: clocking ongoing items

[Brian van den Broek]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On 14 Dec 2012 01:52, "Rainer Stengele" <rainer.stengele@online.de> wrote:
>
> Hi all!
>
> I wonder how others are clocking ongoing isues, which are not really
todos but more like "issues" collecting clocked time for work done
regularly.
> Example: Reading mail and organising daily priorities of tasks.
> This "todo" will not finish very soon.
> I want this item to be clocked daily but do not want it to look like a
standard todo.

Hi Rainer,

Why do you not want them as TODOs? I had thought I didn't but came to
believe I was over-complicating things.

I have a number of daily and weekly tasks of this sort (these include your
examples), and they are genuinely things I need to do :-) They have
appropriate repeater cookies in the scheduled lines and it works just fine.
Well enough that I've forgotten the reasons for which I resisted treating
them as TODO items in the first place.

Best,

Brian vdB

[-- Attachment #2: Type: text/html, Size: 1111 bytes --]

Re: clocking ongoing items

[William Gardella]

Hi Rainer,

Rainer Stengele <rainer.stengele-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org> writes:

> Hi all!
>
> I wonder how others are clocking ongoing isues, which are not really
> todos but more like "issues" collecting clocked time for work done
> regularly.  Example: Reading mail and organising daily priorities of
> tasks.  This "todo" will not finish very soon.  I want this item to be
> clocked daily but do not want it to look like a standard todo.  How do
> others handle this? I remember Bernt once had a tag "ONGOING" which he
> dropped again.
>
> Cheers,
> Rainer
>
>
>

Your use case sounds like a good fit for the `org-habit' module.  See
(info "(org) Tracking your habits").  A habit is like a periodic TODO
which you mark DONE each time you complete it for the day, but it resets
itself to being "undone" again after an interval of time passes.  Habits
also come with a nice display in agenda views to show you how often you
actually do something.  (I use this feature to track my daily meditation
habits, for example).  This way, together with org's time clock, the
task is periodic, but the clock times and relevant notes can still all
be kept in one place and the task can be represented as a single
headline.

Best,

-- 
WGG
I use grml (http://grml.org/)

Re: clocking ongoing items

[Memnon Anon]

Rainer Stengele <rainer.stengele@online.de> writes:

> I wonder how others are clocking ongoing isues, which are not really
> todos but more like "issues" collecting clocked time for work done
> regularly. Example: Reading mail and organising daily priorities of
> tasks. 

*** STRT [#C] Reading Mail/News
    <2012-12-14 Fr .+1d>
[...]
*** STRT [#C] Tagesplanung
    <2012-12-14 Fr .+1d>

At first, I, too, thought these 'issues' are different, but I do not
anymore.

Memnon

Re: clocking ongoing items

[Rainer Stengele]

Am 14.12.2012 07:51, schrieb Rainer Stengele:
> Hi all!
> 
> I wonder how others are clocking ongoing isues, which are not really todos but more like "issues" collecting clocked time for work done regularly.
> Example: Reading mail and organising daily priorities of tasks.
> This "todo" will not finish very soon.
> I want this item to be clocked daily but do not want it to look like a standard todo.
> How do others handle this? I remember Bernt once had a tag "ONGOING" which he dropped again.
> 
> Cheers,
> Rainer
> 
> 
> 
Ok, I surrender .. I force myself thinking that this is also a todo ..
What I did was to prevent changing the TODO status to NEXT when clocking
in, as there is no real next action.

Thanks,
Rainer