emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bernt Hansen <bernt@norang.ca>
To: Richard Riley <rileyrgdev@googlemail.com>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: representation of clients
Date: Mon, 07 Sep 2009 21:27:15 -0400	[thread overview]
Message-ID: <87y6oqtedo.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <4aa47bfa.0b38560a.15f1.42f4@mx.google.com> (Richard Riley's message of "Mon\, 07 Sep 2009 05\:20\:24 +0200")

Richard Riley <rileyrgdev@googlemail.com> writes:

> People using org-mode to maintain tasks, order, reminders , notes etc,
> how do you represent clients? By a TAG? by a separate category? Separate
> file?

All of the above.  http://doc.norang.ca/org-mode.html#sec-2.3

I tend to keep one file per client, with a #+FILETAGS entry for the
client and set the category just so it's easy to see in the agenda what
tasks apply to what client.

I use the category to visually see what client a task belongs to on the
agenda quickly.

I use tags to filter tasks on the agenda.

I use entire files to group tasks for a client so they can be
added/removed from the agenda easily.

So for every client project file I'll have the main file and an archive
file to keep the entire history of whatever I've worked on in the past.
Archive dead stuff to keep the agenda response time fast.

Adding and removing clients from the agenda is simply adding and
removing entire files from org-agenda-files.

I have a client X that has multiple clients (A, B, C, D, etc), and I
work on their client's systems.  In this case I have org files X-A.org,
X-B.org, ... , X-D.org since their clients come and go and I want to
only keep the stuff I work on in my agenda.  Similarly I'll also have an
X.org for stuff specific to the main client that I work for.

Hope some of that makes sense :)

-Bernt

     prev parent reply	other threads:[~2009-09-08  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07  3:20 representation of clients Richard Riley
2009-09-07  4:38 ` Russell Adams
2009-09-07  8:59 ` Sebastian Rose
2009-09-08  1:27 ` Bernt Hansen [this message]

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=87y6oqtedo.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.com \
    /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

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).