Org-mode mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Wed, 23 Jan 2013 09:59:14 +0800
Message-ID: <87obgg4q31.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CD24B2F0.13D05%Elwood151@web.de>

M <Elwood151@web.de> writes:

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

This is exactly what I do, and it works great for me. If you enable
state-change logging for the TODO keywords you use most, you can keep a
fully annotated and time-stamped history of how the TODO has progressed.
I make the heading something generic (ie, "Article XYZ") and note what
has to be done next in the logbook.

I like the idea of a single TODO for a single "thing", even if that
thing has multiple steps. I often don't know what those steps are going
to be (arguments over email, waiting for someone to get back from
vacation, blocking on another task, etc) so I need flexibility.

In practice, most of my complex tasks start at TODO, bounce back and
forth between NEXT and WAITING, and finally end up at DONE. Changes
between WAITING and NEXT are logged, so I end up with a LOGBOOK full of
neatly stamped changes, each one with a description (plus links to
emails and all) of progress. This "feels right" to me.

My main custom agenda view has a block each for WAITING and NEXT
headings.

> Would there be a way to make the "children" inherit automatically a text
> from the project name, e. g.

Wouldn't this be best taken care of with tags and tag inheritance? I
also put colleagues' names in tags, when something requires their
participation, which makes it easy get a view of "stuff John should be
doing".

The problem with the logbook approach is that logbook entries are fairly
limited beasts (you can't tag them, for instance), and I'm probably
already on the verge of abusing them. Next on my list would be sorting
agenda items by timestamp of most recent log entry, and also an agenda
hotkey to display the most recent log entry for the TODO under point.

Possibly what I should be considering is a state-change trigger that
actually creates a sub-heading TODO, rather than a logbook entry.

Hope something in there's useful!

Eric

  parent reply	other threads:[~2013-01-23  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 20:19 M
2013-01-22 21:14 ` 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 [this message]
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://orgmode.org

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obgg4q31.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://orgmode.org/list/0 list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ https://orgmode.org/list \
		emacs-orgmode@gnu.org
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.orgmode
	nntp://news.gmane.io/gmane.emacs.orgmode


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git