emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: "Hellekin O. Wolf" <hellekin@cepheide.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: AutOrg, and practice of GTD in a group
Date: Tue, 22 Jun 2010 18:09:36 -0400	[thread overview]
Message-ID: <87631ag1nj.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <20100622211941.GF520@now.cepheide.org> (Hellekin O. Wolf's message of "Tue\, 22 Jun 2010 21\:19\:41 +0000")

"Hellekin O. Wolf" <hellekin@cepheide.org> writes:

> How do you guys use CATEGORIES, PROPERTIES and TAGS in combination
> with TODO states and Org-Agenda to optimize your GTD workflow?

I use CATEGORIES mainly as a visual cue in my agenda to help categories
tasks.  Other than that it doesn't really do anything in my setup.

TAGS I use for context and other convenient filters for grouping tasks.
You can easily filter (removing or adding tasks) in the agenda by tag.

I use PROPERTIES for effort estimates, blocking control, recording when
tasks repeated last (for cyclic tasks) etc.

TODO states are for action items (TODO, NEXT, DONE, CANCELLED, WAITING
etc).

> What strategy do you take when you have a personal SEQ_TODO and need
> to work with other people, using a different SEQ_TODO?

I would defined the SEQ_TODO in the file with #+TODO: TODO NEXT | DONE
(or whatever is appropriate for that file).  That overrides any global
todo settings.

All of my gory setup details are at http://doc.norang.ca/org-mode.html

HTH,
Bernt

  reply	other threads:[~2010-06-22 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:19 AutOrg, and practice of GTD in a group Hellekin O. Wolf
2010-06-22 22:09 ` Bernt Hansen [this message]
2010-06-23 17:41   ` Hellekin O. Wolf
2010-06-23  6:41 ` Sven Bretfeld
2010-06-24 13:00   ` Hellekin O. Wolf
2010-06-24 13:21     ` Jason McBrayer
2010-06-27 20:16     ` Sven Bretfeld

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=87631ag1nj.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=hellekin@cepheide.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).