From: Ihor Radchenko <yantar92@posteo.net>
To: Sven Bretfeld <sven.bretfeld@ntnu.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: Strategic time planing: Breaking down EFFORT property
Date: Wed, 04 Oct 2023 11:21:07 +0000 [thread overview]
Message-ID: <87o7hemy58.fsf@localhost> (raw)
In-Reply-To: <87fs2qke98.fsf@ntnu.no>
Sven Bretfeld <sven.bretfeld@ntnu.no> writes:
> ...
> Now, it is the beginning of the first week of October. I make my weekly
> planning and decide to spent 15 hours of this week with Project 1 and 5
> with Project two. Today I would want to work on Project 1 for 4 hours, 3
> on Project 2. I'm clocking in to Project 1, setting a org-clock-alarm to
> remind me when it is time to switch to Project 2:
>
> * Project 1
> :PROPERTIES:
> :EFFORT_TOTAL: 100:00
> :EFFORT_THIS_MONTH: 54
> :EFFORT_THIS_WEEK: 15
> :EFFORT_TODAY: 4
> :CLOCK_MODELINE_TOTAL: today
> :END:
> DEADLINE: <2023-12-24>
> ...
> Does anybody have an idea how to realize this scenario?
I am not sure what you mean by `org-clock-alarm'. We have
`org-clock-sound', which you need to customize for alarm to be played
when clocked time exceeds EFFORT.
For weekly/monthly/total, you can use clock tables to summarize the time
spend on different projects during the week/month/in total. See
https://orgmode.org/manual/The-clock-table.html
You can display additional property values in the clock table using
:properties attribute. That will allow seeing clocked time and your
estimates stored in EFFORT_* properties.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-04 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 7:10 Strategic time planing: Breaking down EFFORT property Sven Bretfeld
2023-10-04 11:21 ` Ihor Radchenko [this message]
2023-10-04 22:28 ` Sven Bretfeld
2023-10-05 4:59 ` Dr. Arne Babenhauserheide
2023-10-05 11:53 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7hemy58.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=sven.bretfeld@ntnu.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.