From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Clocking work time vs. office time
Date: Fri, 29 Apr 2016 10:16:52 +0100 [thread overview]
Message-ID: <87h9ek3hbv.fsf@ucl.ac.uk> (raw)
In-Reply-To: 8a62af79ec0b4d3d9e2c2e83a053f889@HE1PR01MB1898.eurprd01.prod.exchangelabs.com
Hi Marcin,
I am not sure if this will help but...
I keep clocking information completely separate from the individual
tasks. This may go against the grain for typical org usage but it works
for me.
I have a clocking hierarchy defined which includes headlines for
each project etc. and clock these in and out as required. The actual
task contents for each task will appear in separate files that have no
clocking information. This then frees me to up to have whatever clocking
structure I want. I do this because the reporting information that I
need to provide does not actually align with the real tasks in my case
so my separate clocking hierarchy provides a different "view" into my
tasks.
In your case, you could have something like this for the "tasks" you
will clock:
#+begin_src org
,* office
,** task a
,** task b
,** task d
,* out of office
,** task a
,** task c
#+end_src
where, in this case, tasks b and d are only done in the office, task c
only outside/remotely and task a can take place in either place. It
means duplicating the headlines that could appear in either site but the
actual task detail etc. is somewhere else and not duplicated.
You could put links in each headline to the actual task contents for
easy navigation, of course.
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-739-g789412
next parent reply other threads:[~2016-04-29 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a62af79ec0b4d3d9e2c2e83a053f889@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-29 9:16 ` Eric S Fraga [this message]
2016-04-29 9:25 ` Clocking work time vs. office time Marcin Borkowski
[not found] ` <7b8632d87e0d414e8c12b27aee1452b9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-29 11:05 ` Eric S Fraga
2016-04-29 12:08 ` Loris Bennett
2016-04-29 12:31 ` Peter Neilson
2016-04-29 14:23 ` Marcin Borkowski
2016-04-29 12:24 ` Marcin Borkowski
2016-04-29 15:13 ` Stefan Nobis
2016-04-29 19:58 ` Marcin Borkowski
2016-04-29 7:29 Marcin Borkowski
2016-04-29 9:21 ` Michael Welle
2016-04-29 14:26 ` Marcin Borkowski
2016-04-29 14:51 ` Brett Viren
2016-04-29 18:00 ` Michael Welle
2016-05-02 20:39 ` Marcin Borkowski
2016-04-29 18:10 ` Michael Welle
2016-04-29 19:55 ` Marcin Borkowski
[not found] ` <17pdvcxts5.ln2@news.c0t0d0s0.de>
2016-04-30 6:28 ` Marcin Borkowski
2016-04-29 20:13 ` Simon Thum
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=87h9ek3hbv.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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.