From: M <Elwood151@web.de>
To: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 21:19:44 +0100 [thread overview]
Message-ID: <CD24B2F0.13D05%Elwood151@web.de> (raw)
Hi,
I'm working with org-mode to document my work and to keep track of tasks and
projects.
At the moment there are many little projects where I
* get a text from someone (or write it myself)
* have to read and edit it
* send it oer email to 1 or 2 other colleagues which have to read / edit it
* get it back and check the changes
* maybe send the text again to the original author
* then finally release the text for publication
... and you imagine, there is not only 1 such text at once but several of
them.
I wonder what is an approriate way to keep track of such workflows with
org-mode..
I'm using MS Outlook for mails and so when I receive a mail, I store a
hyperlink pointing to that mail in Outlook.
For a process like the one above I would have a task
* TODO Write Text about topic XY and send it to colleague(s)...
then
* WAIT Colleage(s): Feedback on Text about topic XY
* TODO check feedback/changes of Colleagues and edit again, and send for
approval
* TODO send to original author
* WAIT for Feedback of original author
(if changes, repeat process above)
* TODO send text to publishing colleague
or similar...
I hope it is clear what I mean, there are a lot of small steps and each time
creating a new task takes much time and I have to copy the name of the
"project" again and again...
Maybe it would be better to add all the notes about the progress as notes in
the Logbook and change the Heading of the task each time, but that also
seems strange to me...
Would there be a way to make the "children" inherit automatically a text
from the project name, e. g.
* Text about topic XY for publishing in ABC
** WAIT John: Feedback on Text about topic XY for publishing in ABC
** Send Text about topic XY for publishing in ABC to Ellen for approval
...
in a way that " Text about topic XY for publishing in ABC" is filled in
automatically by a placeholder?
Or what is your way for tracking such workflows in org-mode?
Kind regards
Martin
next reply other threads:[~2013-01-22 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:19 M [this message]
2013-01-22 21:14 ` How to deal with small projects which are often changing their status/ person Thorsten Jolitz
2013-01-22 21:39 ` Nicolas Richard
2013-01-22 21:56 ` Thorsten Jolitz
2013-01-22 21:40 ` M
2013-01-22 21:55 ` Thorsten Jolitz
2013-01-23 8:59 ` Tomas Hlavaty
2013-01-23 10:20 ` OT: using ZIP based files with git (was: How to deal with small projects which are often changing their status/ person) Karl Voit
2013-01-22 21:39 ` How to deal with small projects which are often changing their status/ person Thomas S. Dye
2013-01-22 22:27 ` M
2013-01-22 22:49 ` Thomas S. Dye
2013-01-23 1:59 ` Eric Abrahamsen
2013-01-23 9:15 ` Julian Burgos
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=CD24B2F0.13D05%Elwood151@web.de \
--to=elwood151@web.de \
--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).