From: Daryl Manning <dwm+orgmode@wakatara.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Cc: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Subject: Re: GTD and CRM workflow for org-mode using Agenda and org-super-agenda [followup]
Date: Mon, 13 May 2019 17:26:11 +0700 [thread overview]
Message-ID: <CAL9aZksgVfjC1UwQ8BFhesRH+5peQhQLaVd2LkH9LYSn_qjjvw@mail.gmail.com> (raw)
In-Reply-To: <xuu6pnomaeqp.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
Thanks! That's quite kind. Just glad to know someone found it useful.
The DEADLINE with an intermediary step would be cool. The only thing I
could think of that might make something like that work is if you might
create a "subtask" that had the DEADLINE and then follow that and resolve
before the actual top level task got resolved, though being a relative
newcomer to org-mode, I have absolutely not a clue how you'd do accomplish
that (sorry). I'm sure there is probably a better way. =]
Rather than using a note, btw, I've found it much more useful to signify
delegatee with a tag (so, something like :jones:). The advantage is when
you have a meeting with someone or need to refer to their stuff, just sort
all tasks/todos by tag :jones" and you know everything Jones is on the hook
for. I also generally keep a file for someone - usually to organize 1:1
notes and similar and use a setup like:
# jones.org
``` elisp
#+TITLE: Jones
* Jones
:jones:loka:
** Jones 1:1 - 2019-05-03
*** Team Structure and Leads shifts
*** PMS reviews
*** Martech
...
```
Also very handy if you put the TODOs inline with the 1:1 notes as they'll
still be tagged to find them from the personnel buffer.
Anyhow, YMMV but that has worked surprisingly well though it does not solve
your *actual* intermediary/delegated DEADLINE step. Sorry. =]
ciao!
Daryl.
On Mon, May 13, 2019 at 4:24 PM Fraga, Eric <e.fraga@ucl.ac.uk> wrote:
> On Monday, 13 May 2019 at 10:50, Daryl Manning wrote:
> > A surprising (to me, anyway) number of people asked me privately to
> follow
> > up about my setup and how I was using thing, so I promised I would put a
> > blog post together (I had a draft from march anyhow... =] ).
>
> Thanks for this. Very interesting and well written. It's given me some
> things to think about.
>
> The one feature that I am missing is chained TODOs in the following
> context. Like you, I spend an inordinate amount of time chasing
> people. I often have tasks that I delegate. I change the task to WAIT
> from TODO and add a note that says to whom I have delegated the
> task. The original task will typically have a DEADLINE but I would like
> to associate a deadline for the delegated step. This is not easy to
> do. For instance, I cannot store a link from the agenda view which
> would allow me, from that view, to easily create a new linked task.
>
> Anyway, thanks again.
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.2.2-290-g300f15
>
[-- Attachment #2: Type: text/html, Size: 3390 bytes --]
next prev parent reply other threads:[~2019-05-13 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 3:50 GTD and CRM workflow for org-mode using Agenda and org-super-agenda [followup] Daryl Manning
[not found] ` <xuu6pnomaeqp.fsf@ucl.ac.uk>
2019-05-13 10:26 ` Daryl Manning [this message]
2019-05-13 11:45 ` Fraga, Eric
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL9aZksgVfjC1UwQ8BFhesRH+5peQhQLaVd2LkH9LYSn_qjjvw@mail.gmail.com \
--to=dwm+orgmode@wakatara.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).