From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Incident tracking
Date: Fri, 28 Feb 2020 09:26:06 -0600 [thread overview]
Message-ID: <CAFAhFSUFrNJsQbS88jQefDHqxWqWLWJ2ARQc+_X7AuoB5uVobg@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8vVZLS2uYU61wWOvuZ6GEYQHd-v_PX3fe3r0LdXRyKO-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
I can see that an "incident" can be seen as a TODO; indeed, anything event
can start as a TODO, then move on in status to one of your other
org-todo-keyword entries. Question: When I start the TODO process, and then
update the status, once or more times, finally, perhaps with DONE, is there
a record of this "Werdegang," this process?
On Thu, Feb 27, 2020 at 7:50 PM Samuel Wales <samologist@gmail.com> wrote:
> i have no right to respond as i have 483 scheduleds and 28 deadlines
> and i get lost even trying to get one thing done per week, but i just
> wanted to add to the advice so far.
>
> there is org-edna for dependencies. org-depend also, but i think it
> lacks the feature of scheduling a remote org-id header once a local
> one is doneified.
>
> it is useful to stick inactive timestamps at boh on headlines, so you
> can do all sorts of things like visually bisect to find what you are
> looking for, search only the visible headlines, etc. this makes for
> good logging. [others will recommend date trees instead.]
>
> i like this type of discussion as we have had few of them in the last
> 8 years or so and there is much insight for usage and even fodder for
> better features or refactoring, i think.
>
> gtd is too labor-intensive for myself, but others will suggest reading
> materials if you think it fits.
>
> org is flexible so it's really a toolkit for figuring out your own
> structures. i'd suggest not getting too fancy at first because yagni
> sometimes applies.
>
> ===
>
> i find it useful to think of my org forest as an ontology of
> representations of preferably physical objects that become canonical
> locations in it.
>
> thus, your washer is one holon [subtree] and you always know where to
> refile to for it. then you don't need tags as much; you can use org
> id links to make the forest a digraph. location determines identity.
>
> this is in contrast to, for example "stuff to do for maintenance".
>
> --
> The Kafka Pandemic
>
> What is misopathy?
>
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>
[-- Attachment #2: Type: text/html, Size: 2672 bytes --]
next prev parent reply other threads:[~2020-02-28 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:55 Incident tracking Lawrence Bottorff
2020-02-27 23:28 ` Russell Adams
2020-02-28 1:00 ` Tim Cross
2020-02-28 1:50 ` Samuel Wales
2020-02-28 15:26 ` Lawrence Bottorff [this message]
2020-02-28 16:28 ` Russell Adams
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=CAFAhFSUFrNJsQbS88jQefDHqxWqWLWJ2ARQc+_X7AuoB5uVobg@mail.gmail.com \
--to=borgauf@gmail.com \
--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).