From: Adrian Bradd <adrian.bradd@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Handling tasks that span multiple projects
Date: Sun, 5 Mar 2017 11:00:05 -0500 [thread overview]
Message-ID: <CAMYmr8zfm-nwV=8MtGQ_0pW8v7Enx6XHzK9K9xBwMxQFYO7-_g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Hello,
I have seen examples of GTD or GTD-like workflows that use a project based
management system like below:
* Project 1
** Tasks
* Project 2
** Tasks
* Tasks
* Incoming
In my work I typically encounter a task that is common to multiple
projects. I haven't found any example of how to handle this in a GTD
workflow. I use tags to note a task that is common to multiple projects,
but would like the physical structure as well. Copying the same task into
multiple project hierarchies doesn't make much sense to me as I would need
to update the same task twice, unless there was some way to synchronize
them. Does anyone have references or ideas about how to handle this?
[-- Attachment #2: Type: text/html, Size: 830 bytes --]
next reply other threads:[~2017-03-05 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 16:00 Adrian Bradd [this message]
[not found] <91989a77d7ae4d6ea40736d1e8c032c9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-05 17:04 ` Handling tasks that span multiple projects Eric S Fraga
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='CAMYmr8zfm-nwV=8MtGQ_0pW8v7Enx6XHzK9K9xBwMxQFYO7-_g@mail.gmail.com' \
--to=adrian.bradd@gmail.com \
--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).