Handling tasks that span multiple projects

Handling tasks that span multiple projects

[Adrian Bradd]

[-- 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 --]

Re: Handling tasks that span multiple projects

[Eric S Fraga]

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

I tend to not have a project hierarchy but instead use tags to identify
projects so that a given task can belong to more than one project.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]